[Mono.Android] Bind API-35 Beta 2.

[jpobst]

Context: https://developer.android.com/about/versions/15
Context: https://android-developers.googleblog.com/2024/05/the-second-beta-of-android-15.html

Android 15 Beta 2 has been released. The Android 15
Developer Preview Program Overview Timeline and updates section
suggests the following timeline:

• Feb/Mar: Developer Previews
• April/May: Unstable Betas
• June/July: Stable Betas
• ???: Final

This will be usable in its preview form to .NET 9 Preview users who explicitly target net9.0-android35.

[jonpryor]

Wouldn't it be better to add eventName metadata to explicitly name the event, vs. renaming the method name itself?

[jpobst]

Unfortunately, it isn't the event itself that is the problem[1], it's the EventHandler name in the internal *ListenerImplementor that is the problem:

[global::Android.Runtime.Register ("mono/android/app/AppOpsManager_OnOpActiveChangedListenerImplementor", ApiSince = 30)]
internal sealed partial class IOnOpActiveChangedListenerImplementor : global::Java.Lang.Object, IOnOpActiveChangedListener
{
    public EventHandler<OpActiveChangedEventArgs>? OnOpActiveChangedHandler;

    public void OnOpActiveChanged (string op, int uid, string packageName, bool active)
    {
    	var __h = OnOpActiveChangedHandler;
    	if (__h != null)
    		__h (sender, new OpActiveChangedEventArgs (op, uid, packageName, active));
    }

    // Duplicate OnOpActiveChangedHandler
    public EventHandler<OpActiveChangedEventArgs>? OnOpActiveChangedHandler;

    public void OnOpActiveChanged (string op, int uid, string packageName, string? attributionTag, int virtualDeviceId, bool active, int attributionFlags, int attributionChainId)
    {
    	var __h = OnOpActiveChangedHandler;
    	if (__h != null)
    		__h (sender, new OpActiveChangedEventArgs (op, uid, packageName, attributionTag, virtualDeviceId, active, attributionFlags, attributionChainId));
    }
}

[1] I can't find anything that actually generates events for this listener (ie: no SetOnOpActiveChangedListener method anywhere). If that existed then the event name would likely also be a problem.

[jpobst]

Previously, we have also just removed these new methods, as they are default interface methods, so we could do that here as well:

https://github.com/xamarin/xamarin-android/blob/ef31401a44311ed49cee9df1e207918226b4c745/src/Mono.Android/metadata#L1701-L1703

[jonpryor]

Also not sure I like count(parameter)=8, as if they add an 8-parameter overload in the future, it'll match.

"Safer" would likely to use //method/@jni-signature.

[jpobst]

Updated to use the "full" generated metadata path.

[jonpryor]

Draft commit messages:

Context: https://developer.android.com/about/versions/15
Context: https://android-developers.googleblog.com/2024/05/the-second-beta-of-android-15.html
Context: d5b608e8e0c25816d4c5d8df6488ab4d021bd41c

Android 15 Beta 2 was released on 2024-May-15:

  * [API-VanillaIceCream Beta 2 vs. API-34][1]
  * [API-VanillaIceCream Beta 2 vs. Beta 1][2] (d5b608e8)

The Android 15 Developer Preview [Timeline and updates][0] section
suggests the following timeline:

  * Feb/Mar: Developer Previews
  * April/May: Unstable Betas
  * June/July: Stable Betas with a [Platform Stability milestone][3]
    expected in Beta 3
  * ???: Final

Beta 2 be usable in its preview form to .NET 9 Preview 5 users who
explicitly target `net9.0-android35`.

[0]: https://web.archive.org/web/20240514210701/https://developer.android.com/about/versions/15/overview#timeline
[1]: https://developer.android.com/sdk/api_diff/v-beta2/changes
[2]: https://developer.android.com/sdk/api_diff/v-beta2-incr/changes
[3]: https://web.archive.org/web/20240514210701/https://developer.android.com/about/versions/15/overview#platform_stability