Rename SBRP after consolidation with SBE

[MichaelSimons]

Possible names

source-build-assets
source-build-packages

[MichaelSimons]

One thing to consider is what is a better approach, renaming versus creating a new repo and deprecating SBRP. Either approach is a non-trivial amount of work. The benefit of a rename is that with GH you will get redirects but a rename has the potential to affect servicing in places where the redirect does not work. Renames aren't trivial but aren't impossible. You rename the repo on GitHub, then in AzDO. Then update mirroring. That should then take care of the official build logic. You then need to update all of the dependency flow (not too hard). And then you need to find all the places that may have relied on the old names for build logic.

This should be done prior to RC1 else wait until .NET 11 to reduce unnecessary risk IMO. Given the ROI on this, I lean towards 11.

[MichaelSimons]

[Triage] - This does not meet the bar for 10 given the other priorities. It should be done first thing in 11. Renaming seems the preferred direction.

[NikolaMilosavljevic]

Here's the rough outline of required steps:

1. Rename the github repo - to source-build-assets
2. Add an AzDO repo for the new name - dotnet-source-build-assets
3. Add mirroring for the new SBRP name - continue mirroring for the old SBRP name.
4. Add new pipelines for the new internal repo - public pipelines would continue to work
5. Update all AzDO consumer repos to use the new repo name - i.e. infra changes in 8.0 (installer), 9.0 (sdk) and 10.0 (vmr) - make changes in AzDO repos.
6. Update .NET 11 VMR to point to the new SBRP name - make changes in AzDO VMR repo.
7. Create new public pipelines and delete old ones