fix: use persistent=false on Android 16 to prevent system phone process crash

[xiemobiao]

Summary

• On Android 16 (SDK 36), calling overrideConfig(persistent=true) crashes the com.android.phone system process with SecurityException: overrideConfig with persistent=true only can be invoked by system app
• The crash occurs in a different process (com.android.phone, not the app itself), so the existing try-catch in BrokerInstrumentation.kt cannot catch it
• This fix checks Build.VERSION.SDK_INT and uses persistent=false on Android 16+, preventing the crash entirely

Changes

• BrokerInstrumentation.kt: Replace try-catch fallback with SDK version check, use persistent=false directly on API 36+
• Moder.kt: Apply the same fix to overrideConfigDirectly()

Test plan

• Tested on Pixel 10 Pro XL, Android 16 (BP4A.260205.001, security patch 2026-02-05)
• VoLTE, VoNR, VoWiFi toggle works without crash
• 5G SA (NR_SA) successfully connected on China Unicom
• Shizuku 13.6.0 required for Android 16 compatibility

🤖 Generated with Claude Code

[yhkee0404]

It seems the boolean value of persistent in BrokerInstrumentation does not have to be evaluated at all because it is always false following the current implementation of overrideConfigUsingBroker, and the boolean value of persistent evaluated all the time as false on Android 16 (SDK 36) following the current implementation of overrideConfigDirectly may also discourage users who have not applied the troublesome security patches and therefore are still free to set it true.