fix(android): preserve typed JVM memory failures during loading

Translate actual OutOfMemoryError at the bridge boundary before upstream stringifies it. Preserve observed heap bytes, missing reasons, coroutine context and cancellation; retain SessionHolder ownership and load options. Restrict heap-specific remediation to known heap reasons and parse named bridge failure contracts once.

Coordinate bridge protocol v4, clarify doctor configuration versus target capacity, and preserve the memory primary across cleanup failure/retry. Verify controlled immediate/late/inline continuation outcomes with the pinned JAR and real JDK, focused tests, and tiny real CLI/MCP method workflows.

Actual heap exhaustion, the reported APK, pre-handshake failures, Linux and Windows remain unverified; no stress or profiling run.

Fixes #3517

scripts/verify/android/metadata.mjs

@@ -65,6 +65,10 @@ export const verifyAndroidMetadata = async ({
       ],
       { timeout: 120_000, maxBuffer: 8 * 1024 * 1024 },
     );
+    assert.match(
+      result.stdout,
+      /LOAD_FAILURE_REGRESSION_PASS typed=true decoy=true suspension=true cancellation=true/u,
+    );
     assert.match(
       result.stdout,
       /METADATA_REGRESSION_PASS classes=\d+ overloads=3/u,