Use Assert.Inconclusive for emulator acquisition failures

Emulator acquisition failures are infrastructure issues, not test
failures. Using Assert.Inconclusive instead of Assert.IsTrue marks
these as skipped/inconclusive rather than turning the build red.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jonathanpeppers

src/Xamarin.Android.Build.Tasks/Tests/Xamarin.Android.Build.Tests/Utilities/DeviceTest.cs

@@ -174,7 +174,9 @@ public static void RestartDevice ()
 			// shell out to msbuild and start the emulator again
 			var dotnet = new DotNetCLI (Path.Combine (XABuildPaths.TopDirectory, "src", "Xamarin.Android.Build.Tasks", "Tests", "Xamarin.Android.Build.Tests", "Emulator.csproj"));
 			dotnet.ProjectDirectory = XABuildPaths.TestAssemblyOutputDirectory;
-			Assert.IsTrue (dotnet.Build ("AcquireAndroidTarget", parameters: new string[] { "TestAvdForceCreation=false", $"Configuration={XABuildPaths.Configuration}" }), "Failed to acquire emulator.");
+			if (!dotnet.Build ("AcquireAndroidTarget", parameters: new string[] { "TestAvdForceCreation=false", $"Configuration={XABuildPaths.Configuration}" })) {
+				Assert.Inconclusive ("Failed to acquire emulator.");
+			}
 			WaitFor ((int)TimeSpan.FromSeconds (5).TotalMilliseconds);
 		}