Fix cold-start ANR: resolve the native crash handler without reading the APK

[melekr]

Problem

Native crash-handler path resolution synchronously opened the application's base APK and candidate split APKs with Java ZIP APIs.
Opening large APKs can parse their ZIP central directories on the calling thread and delay application startup.

Fixes

• Add Native crash-handler test coverage #222
• Resolve the native-library path selected by Android's linker.
• Prefer an existing extracted native library.
• Use installed split metadata only as fallback.
• Do not open or parse the base APK or split APK ZIP contents.
• Use the running process ABI when fallback construction requires one.
• Compare split candidates globally and reject ambiguous matches.
• Contain optional-native setup, disable, and dump failures.
• Preserve managed reporting when native integration is unavailable.
• Restart native uploads after disable followed by enable.
• Sanitize native failure diagnostics.

API behavior

• Existing void enableNativeIntegration(...) APIs remain compatible.
• tryEnableNativeIntegration(...) reports whether native registration succeeded.
• dumpWithoutCrash() is safe while native integration is unavailable or disabled.
• Initialization remains synchronous and process-scoped.

Docs

https://docs.saucelabs.com/error-reporting/platform-integrations/android/native-crash-integration/

Compatibility

• Minimum Android API remains 21.
• Monolithic APK and Android App Bundle installations are supported.
• x86_64, armeabi-v7a, and arm64-v8a remain supported, x86 native capture remains unsupported.
• Flexible 16 KB page-size support is preserved.

ref: BT-7431
ref: BT-7447
ref: BT-7448
ref: BT-7449
ref: BT-7450
ref: BT-7458
ref: BT-7472