[tests] Be more flexible when parsing build-tools versions

[pjcollins]

Context: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3520928&view=ms.vss-test-web.build-test-results-tab&runId=11613622&resultId=100500&paneView=debug

Xamarin.Android.Build.Task tests which attempt to look up the path to
aapt/aapt2 recently started failing on the Azure Pipelines hosted macOS
machine pool [0]. I suspect this is caused by a preview version of tools
ending up on the machine. I think we can be a bit more lenient when
locating the latest version of build-tools by instead using a string
comparison. This will also allow the relevant tests to use a preview
version of build-tools if they exist. Additional logging has also been
added to confirm this hypothesis.

[0]:

System.FormatException : Input string was not in a correct format.
    at System.Number.ThrowOverflowOrFormatException (System.Boolean overflow, System.String overflowResourceKey) [0x0001a] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Number.ParseInt32 (System.ReadOnlySpan`1[T] value, System.Globalization.NumberStyles styles, System.Globalization.NumberFormatInfo info) [0x00016] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Int32.Parse (System.ReadOnlySpan`1[T] s, System.Globalization.NumberStyles style, System.IFormatProvider provider) [0x0000e] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Version.TryParseComponent (System.ReadOnlySpan`1[T] component, System.String componentName, System.Boolean throwOnFailure, System.Int32& parsedComponent) [0x0000b] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Version.ParseVersion (System.ReadOnlySpan`1[T] input, System.Boolean throwOnFailure) [0x0011a] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Version.Parse (System.String input) [0x00014] in <8855e4c75b1445438dde4104dd4134bb>:0
    at System.Version..ctor (System.String version) [0x00014] in <8855e4c75b1445438dde4104dd4134bb>:0
    at Xamarin.Android.Build.Tests.BaseTest+<>c.<GetPathToLatestBuildTools>b__48_0 (System.String x) [0x00006] in <e6ad3936767d47cea783c180acfe7cf6>:0
    at System.Linq.EnumerableSorter`2[TElement,TKey].ComputeKeys (TElement[] elements, System.Int32 count) [0x00010] in <89222f8e94f04b5cb12f2328985a10a8>:0
    at System.Linq.EnumerableSorter`1[TElement].ComputeMap (TElement[] elements, System.Int32 count) [0x00000] in <89222f8e94f04b5cb12f2328985a10a8>:0
    at System.Linq.EnumerableSorter`1[TElement].Sort (TElement[] elements, System.Int32 count) [0x00000] in <89222f8e94f04b5cb12f2328985a10a8>:0
    at System.Linq.OrderedEnumerable`1[TElement].SortedMap (System.Linq.Buffer`1[TElement] buffer) [0x00006] in <89222f8e94f04b5cb12f2328985a10a8>:0
    at System.Linq.OrderedEnumerable`1+<GetEnumerator>d__3[TElement].MoveNext () [0x0003d] in <89222f8e94f04b5cb12f2328985a10a8>:0
    at Xamarin.Android.Build.Tests.BaseTest.GetPathToLatestBuildTools (System.String exe) [0x00061] in <e6ad3936767d47cea783c180acfe7cf6>:0
    at Xamarin.Android.Build.Tests.BaseTest.GetPathToAapt () [0x00015] in <e6ad3936767d47cea783c180acfe7cf6>:0
    at Xamarin.Android.Build.Tests.ManagedResourceParserTests.CompareAaptAndManagedParserOutputWithCustomIds () [0x000d2] in <e6ad3936767d47cea783c180acfe7cf6>:0

[jonpryor]

Pity this will fails when sorting { "2", "10" }, because it sorts "stringly", not numerically.

Fortunately this is unlikely to be a problem now, because we're likely to always have two digit numbers. (But when we start hitting Build-tools 100, watch out!)

Unfortunately, this also sorts { "29.0.0-rc2", "29.0.0-rc1", "29.0.0" } in that order, such that the -rc2 will be preferred first, over the "stable" 29.0.0 version.

[jonpryor]

Indeed!

https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3522012&view=logs&jobId=cac0e8d3-0ef5-5d2b-b57e-e8fde7204df3&j=b9316caa-d7de-528c-89a6-5db86a60a380&t=ef74b103-60e3-58ea-4723-1595ac528a8c

Found build tools version: /Users/runner/Library/Android/sdk/build-tools/30.0.0-rc1.