[Xamarin.Android.Build.Tasks] Don't report duplicate type if the AssemblyName is the same.

[dellis1972]

Fixes #7473

With the new build system under dotnet we can end up with duplicate assemblies for different RuntimeIdentifiers. This can cause the GenerateJavaStubs task to mistakenly report duplicate types.

warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.AnimatedIcon` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical. [C:\a\1\s\UnoAppAll\UnoAppAll.Mobile\UnoAppAll.Mobile.csproj::TargetFramework=net6.0-android]
error XA4215: The Java type `crc64a5a37c43dff01024.GridViewHeaderItem` is generated by more than one managed type. Please change the [Register] attribute so that the same Java type is not emitted. [C:\a\1\s\UnoAppAll\UnoAppAll.Mobile\UnoAppAll.Mobile.csproj::TargetFramework=net6.0-android]

We should ignore these duplicates if the name of the the type module is the same. If it is then they will be from the same assembly. We cannot use the mvid since that also changes.

[jeromelaban]

@dellis1972 Would you know if this fix going to make it for 7.0.100?

[dellis1972]

@jeromelaban sorry, I got distracted with some other stuff and forgot about this one. I'm not sure if I've missed the 7.0.100 cut off or not. @jonpryor any ideas when the cut off is?

[dellis1972]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jonpryor]

As per https://discord.com/channels/732297728826277939/732297837953679412/1039930020170313921 , this approach may not work at all, because the MVID does change; it's just that it's per-ABI..

I think we need to update <GenerateJavaStubs/> to be "ABI aware", plus other plausible related changes. :-(

[dellis1972]

@jonpryor i reworked this to compage the module name. This stops the error being genereated.

[jonpryor]

This should be able to land for MAUI SR1.

[jonpryor]

Commit message for review:

Fixes: https://github.com/xamarin/xamarin-android/issues/7473

Context: https://github.com/xamarin/monodroid/commit/4c697e5a6b
Context: https://github.com/dotnet/runtime/blob/27c19c31f574375fd1651207b2dc28d39fe1225c/src/libraries/System.Private.CoreLib/src/ILLink/ILLink.Substitutions.64bit.xml

With the .NET 6+ build system, it is possible for an AnyCPU assembly
to become a *set* of assemblies, one per `$(RuntimeIdentifiers)`
value.

In particular, the linker will now *inline* calls to
`System.IntPtr.get_Size()`, replacing them with the appropriate
architecture-specific value.  This means that a single assembly that
uses the `IntPtr.Size` property could become *4* assemblies, one each
for android-arm, android-arm64, android-x86, and android-x64.

Furthermore, each of these assemblies will have a different MVID.

This is "fine", until the assembly contains a `Java.Lang.Object`
subclass that needs a Java Callable Wrapper generated for it, at
which point the `<GenerateJavaStubs/>` task starts emitting XA4214
warnings and XA4215 *errors*:

	warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.AnimatedIcon` exists
	in multiple assemblies: Uno.UI, Uno.UI, Uno.UI, Uno.UI.
	Please refactor the managed type names in these assemblies so that they are not identical.

	error XA4215: The Java type `crc64a5a37c43dff01024.GridViewHeaderItem` is generated by more than
	one managed type. Please change the [Register] attribute so that the same Java type is not emitted.

**Workaround**: Build with only a single `$(RuntimeIdentifier)`:

	dotnet build -p:RuntimeIdentifier=android-arm64 …

Fix this scenario by updating the XA4214 warning and XA4215 error
checks to verify that the module name has changed; if the module name
is the same, then it's not a duplicate type.