ignore Android binding warnings

[bruno-garcia]

Building now creates lots of warnings.

Build succeeded with 1524 warning(s) in 5.4s

Even though the solution had TreatWarningAsErrors, the build passes, which means these warnings are not 'normal' and sneak in and grow over time.

I'm ignoring all warnings that we can't take action (trusting Cursor pretty much on those claims).
But after a few iterations, I couldn't get these types of warnings to break the build, so if new ones are introduced, it'll take someone paying attention and ignoring them explicitly.

Before:

obj/Debug/net9.0-android35.0/api.xml(5156,8): warning BG8701: Invalid return type 'io.sentry.IScope' for member 'Sentry.JavaSdk.Scopes.GetGlobalScope ()'.
      obj/Debug/net9.0-android35.0/api.xml(5157,8): warning BG8701: Invalid return type 'io.sentry.IScope' for member 'Sentry.JavaSdk.Scopes.GetIsolationScope (
      )'.
      obj/Debug/net9.0-android35.0/api.xml(5160,8): warning BG8701: Invalid return type 'io.sentry.IScopes' for member 'Sentry.JavaSdk.Scopes.GetParentScopes ()
      '.
      obj/Debug/net9.0-android35.0/api.xml(5162,8): warning BG8701: Invalid return type 'io.sentry.IScope' for member 'Sentry.JavaSdk.Scopes.GetScope ()'.
      obj/Debug/net9.0-android35.0/api.xml(5167,10): warning BG8801: Invalid parameter type 'io.sentry.IScopes' for member 'Sentry.JavaSdk.Scopes.IsAncestorOf (
      Sentry.JavaSdk.IScopes)'.
      obj/Debug/net9.0-android35.0/api.xml(5219,10): warning BG8801: Invalid parameter type 'io.sentry.ScopeCallback' for member 'Sentry.JavaSdk.Scopes.WithIsol
      ationScope (Sentry.JavaSdk.IScopeCallback)'.
      obj/Debug/net9.0-android35.0/api.xml(5222,10): warning BG8801: Invalid parameter type 'io.sentry.ScopeCallback' for member 'Sentry.JavaSdk.Scopes.WithScop
      e (Sentry.JavaSdk.IScopeCallback)'.
      obj/Debug/net9.0-android35.0/api.xml(5062,10): warning BG8801: Invalid parameter type 'io.sentry.IScope' for member 'Sentry.JavaSdk.Scopes.Scopes (Sentry.
      JavaSdk.IScope, io.sentry.IScope, io.sentry.IScope, java.lang.String)'.
      obj/

Cursors claims:
Turns out there's not much we can do about these, so we'll ignore them

• Enable TreatWarningsAsErrors for Android bindings project reverted
• Suppress expected/unavoidable Android binding warnings (BG8xxx codes)
• These warnings are caused by Java interface circular dependencies in Sentry SDK
• Warnings are documented with explanations for each type
• New warning types will now break the build for review not true
• Analyzed 1528 warnings and confirmed they're due to binding limitations
• Solution preserves existing Metadata.xml strategic type removals

#skip-changelog

[Flash0ver]

suggestion: also mention BG8503 and BG8C00 in the comments

[bruno-garcia]

What should I add as a comment?
Unless there's a plan to fix them, I just want all warnings gone. Should we leave the warnings on the terminal?
Doesn't seem like any of this is worth doing anything about since we're not binding the whole library and it works as inteded

[Flash0ver]

I was thinking about a short description of these warning for completeness.

I added (non-blocking) suggestions.

[Flash0ver]

Suggested change

	<!-- BG8800/BG8700: Unknown/Invalid types - types intentionally removed by Metadata.xml -->
	<!-- BG8800/BG8700: Unknown parameter/return types - types intentionally removed by Metadata.xml -->

Invalid parameter/return types are BG8801/BG8701.