[Xamarin.Android.Build.Tasks] Use class-parse.exe out of MSBuild process

[jpobst]

Context: dotnet/java-interop#499

There are potentially some conflicts with using Xamarin.Android.Tools.Bytecode directly in the MSBuild process, as it now imports protobuf-net which is a commonly used library.

To ensure it isn't running in-process, switch our targets to shell out to class-parse[.exe/.dll].

Additionally add class-parse.dll, etc. to the .NET 6 install pack. We are already shipping class-parse.exe, etc. in the Classic installer even though it wasn't used, so no additional installer changes are needed there.

As expected, moving this out-of-process is slightly slower, but still acceptable.

Before
292 ms  ClassParse                                 1 calls

After
425 ms  ClassParse                                 1 calls

Additionally adds java-resolution-report.log to <FileWrites /> which was added in dotnet/java-interop#849.

[jonathanpeppers]

Could you measure the build time before & after?

I think you could build a binding with -clp:performancesummary or -bl and just see how long this task takes.

[jonathanpeppers]

If class-parse.exe succeeds, should we delete this file immediately? Just leave it on disk if there is a non-zero exit code?

Otherwise, should something delete it when you run the Clean target?

[jpobst]

Good suggestions, added performance data and <FileWrites /> for response file.

[jonathanpeppers]

Looks good if CI ends up green 👍