Align FindSdkManagerPath with FindCmdlineTool discovery order

[rmarinho]

Summary

FindSdkManagerPath() in SdkManager.Packages.cs and FindCmdlineTool() in ProcessUtils.cs use different precedence when resolving cmdline-tools binaries:

Method	Order	Legacy tools/bin fallback
FindSdkManagerPath	Versioned dirs first → latest fallback	✅ Yes
FindCmdlineTool	latest first → versioned dirs fallback	❌ Removed

The FindCmdlineTool order (latest first, no legacy fallback) was set per @jonathanpeppers review in dotnet/android-tools#282. We should evaluate whether FindSdkManagerPath should be updated to match:

1. Check latest first — it is the SDK's own recommended default
2. Remove legacy tools/bin fallback — legacy tools have completely different CLI arguments

References

• PR Add AvdManagerRunner for avdmanager CLI operations android-tools#282 review: Add AvdManagerRunner for avdmanager CLI operations android-tools#282 (comment)
• Copilot observation: Add AvdManagerRunner for avdmanager CLI operations android-tools#282 (comment)
• FindSdkManagerPath: src/Xamarin.Android.Tools.AndroidSdk/SdkManager.Packages.cs:16
• FindCmdlineTool: src/Xamarin.Android.Tools.AndroidSdk/ProcessUtils.cs:240