Site settings UI hooks refactors; Utility class for reflecting members in java; Support fetching DCL states; Set jitless flags based on DCL states and reflect on UI

[quh4gko8]

No description provided.

[inthewaves]

Also, I think it makes more sense to always show the message with the link to Android Settings even if user had it off originally so that users know where it's coming from:

[inthewaves]

CustomOSApis.isExecmemBlocked() is nullable, so null would NPE here

Also should we be using CustomOSApis.isExecmemBlocked() still here? The documentation for it says, "Method obsoleted since 2026050400 release"

    /**
     * Checks if execmem is blocked in current process. Method obsoleted since 2026050400 release.
     * @return true or false if method exists and returns boolean type, null otherwise.
     */
    public static Boolean isExecmemBlocked() {
        return sIsExecmemBlockedMethodCacheWrapper.invoke(null);
    }

Would likely need to replace with isMemoryDclRestricted() for browser child processes and WebView child processes should follow .isWebViewDclRestricted(). Maybe a helper like this with a fallback to obsolete API in the case of older OS versions

private static boolean shouldForceJitless(@LibraryProcessType int type) {
    Boolean restricted = null;
    switch (type) {
        case LibraryProcessType.PROCESS_CHILD:
            restricted = CustomOSApis.isMemoryDclRestricted();
            break;
        case LibraryProcessType.PROCESS_WEBVIEW_CHILD:
            restricted = CustomOSApis.isWebViewDclRestricted();
            break;
    }

    if (restricted == null) {
        restricted = CustomOSApis.isExecmemBlocked();
    }
    return Boolean.TRUE.equals(restricted);
}

[inthewaves]

This should update the Site settings JavaScript JIT UI preference when DCLM is disabled, currently it's shown like this when DCLM is disabled but it was allowed in Vanadium before:

Apply the attached patch

0001-fixup-Reflect-Javascript-JIT-state-also-dependent-on.patch