Move Debug Test first and Clean after runs

[dellis1972]

There is some odd build issue were Release artifacts are making into a Debug build of tests/Mono.Android-Tests/Runtime-Microsoft.Android.Sdk/Mono.Android.NET-Tests.csproj. This only happens in this test project.

I suspect it is because we are overriding the $(Configuration) in the project, but not always since we are also building in a Release environment. Both the top level Configuration.props is using $(Configuration) as well as the test project, but the test project gets a value of Debug from the build yaml. I think it is confusing things, but I have not been able to track it down.

So lets try to clean up the tests/Mono.Android-Tests/Runtime-Microsoft.Android.Sdk/Mono.Android.NET-Tests.csproj test project after it has been built and run. To make sure any old outputs are not there.
Also try running the Debug test first, so its running in a clean environment.

[jonpryor]

I think this link is also related/relevant?

• https://discord.com/channels/732297728826277939/732297837953679412/1291713866409181280

  for the Release builds with runtime linking enabled, libxamarin-app.so shouldn't be produced at all, the one you see in the pack is the "stub" one we build with native code but never ship
  it's built only so that libmonodroid.so we build can link against it
  and then libxamarin-app.so built together with the app conforms to the same ABI and has the same name, so at runtime libmonodroid.so can resolve it
  but none of that takes place with libmonodroid-unified.so - this one has everyhing built into it, including the bits that make up libxamarin-app.so in a regular build
  Debug build should include it, as runtime linking is not enabled - but libmonodroid.so should be the one we build with XA, not the dynamically linked one

[jonpryor]

Context: https://discord.com/channels/732297728826277939/732297837953679412/1291713866409181280
Context: https://github.com/dotnet/android/pull/9006

There are some odd build issue were Release artifacts were present in
the Debug configuration build of
`tests/Mono.Android-Tests/Runtime-Microsoft.Android.Sdk/Mono.Android.NET-Tests.csproj`.

> [when testing with #9006]
> for the `Release` builds with runtime linking enabled, `libxamarin-app.so`
> shouldn't be produced at all, the one you see in the pack is the "stub" one
> we build with `native` code but never ship
> it's built only so that `libmonodroid.so` we build can link against it
> and then `libxamarin-app.so` built together with the app conforms to the same
> ABI and has the same name, so at runtime `libmonodroid.so` can resolve it
> but none of that takes place with `libmonodroid-unified.so` - this one has
> everyhing built into it, including the bits that make up `libxamarin-app.so`
> in a regular build.
> 
> `Debug` build should include it, as runtime linking is not enabled - but
> `libmonodroid.so` should be the one we build with XA, not the dynamically
> linked one

This only happens in this test project.

I suspect it is because we are overriding `$(Configuration)` in the
project, but not always since we are also building in a `Release`
environment.  Both the top level `Configuration.props` is using
`$(Configuration)` as well as the test project, but the test project
gets a value of `Debug` from the build yaml.  I think it is confusing
things, but I have not been able to track it down.

Lets try to clean up the `Mono.Android.NET-Tests.csproj` test project
after it has been built and run, to make sure any old outputs are not
there.

Also try running the `Debug` test first, so that it's running in a
clean environment.