feature: VS drop optimization data fallback

[JanProvaznik]

https://github.com/dotnet/arcade/blob/main/src/Microsoft.DotNet.Arcade.Sdk/tools/VisualStudio.AcquireOptimizationData.targets

These targets specify looking for an optimization drop on the branch where we're building. This does not work on the first build of a branch and requires manual override which is painful for MSBuild that we need to remember this for a release every month.

Proposal: adjust the targets so an override fallback branch can be specified (would be added in msbuild's official build as main) then during the official build it'll search for a branch drop, and if nothing is found then search on fallback branch.

[JanProvaznik]

@SimaTian we discussed this today
@rainersigwald please confirm this is the right approach to our OptProf pains

[rainersigwald]

I would rather move the OptProf data collection to be entirely VS-branch based instead, migrating to VS-owned data collection jobs.