Create automation for re-bootstrapping

[MichaelSimons]

The VMR often needs to be re-bootstrapped during the preview timeframe. We have automation that creates a re-bootstrap PR as part of the release pipeline. It would be ideal if this logic could be refactored in such a way that it can be shared with a new pipeline that we can use to create a re-bootstrap PR at any time. This new pipeline would need to take in a reference to a source-build to pull artifacts from and an installer build to pull the SDK from.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ViktorHofer]

+1. Adding to that: Update the automation to also change the Version.Details.xml file and the global.json msbuild sdk entry for the Arcade dependency.

[ViktorHofer]

One more though, are the steps necessary to bootstrap documented? Especially the part that deals with uploading the artifacts to blob storage. Asking as it would be nice if the product-construction team could also trigger a re-bootstrap so that we don't have to ping your team every time we need a newer Arcade change in arcade or SBRP.

EDIT: Just saw #4247

[mthalman]

+1. Adding to that: Update the automation to also change the Version.Details.xml file and the global.json msbuild sdk entry for the Arcade dependency.

See #4153

[oleksandr-didyk]

Current work done on the issue is in the dev/rework-sb-rebootstrapping branch. Added comments explaining the idea behind the work + describing some details about certain decisions made. Also has a few TODOs for the unknowns left and future work needed to make the release pipeline use the new logic