fix(tasks): resolve CS9377/CS9389 memory-safety errors in monodroid-nativeaot.cs

[omid-io]

Fixes #134115

Description

Under the updated memory safety rules (net11.0 / Roslyn preview diagnostics), src/tasks/AndroidAppBuilder/Templates/monodroid-nativeaot.cs failed to build for Android NativeAOT legs with:

• CS9377: The 'unsafe' modifier does not have any effect on type declarations (MonoDroidExports, JNIEnv, JNINativeInterface, JavaVM).
• CS9389: 'extern' member (AndroidCryptoNative_InitLibraryOnLoad and ManagedMain) must be marked 'unsafe' or 'safe'.

Changes

• Removed obsolete unsafe modifiers from MonoDroidExports, JNIEnv, JNINativeInterface, and JavaVM type declarations.
• Scoped unsafe directly to pointer-bearing JNI entry points and methods (SetEnv, InitRuntime, ExecEntryPoint, FreeNativeResources, GetStringUTFChars, GetJavaVM, GetArrayLength, GetObjectArrayElement).
• Explicitly marked AndroidCryptoNative_InitLibraryOnLoad and ManagedMain as unsafe.

Verification

• Validated with Roslyn C# syntax tree parser (LanguageVersion.Preview) with 0 diagnostics.
• Verified AST structure and explicit unsafe modifier scoping across all affected declarations.

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib
See info in area-owners.md if you want to be subscribed.

[omid-io]

@dotnet-policy-service agree

[azure-pipelines]

Commenter does not have sufficient privileges for PR 134277 in repo dotnet/runtime