Migrate to Arcade publishing infrastructure

[pjcollins]

At the moment we only have limited dependency flow support from dotnet/arcade, and we need to eventually start using all of the arcade publishing infrastructure to facilitate testing and release efforts:

https://github.com/dotnet/arcade/blob/e7ede87875f41a9b3df898ae08da5ebc96e24f56/Documentation/CorePackages/Publishing.md

[rolfbjarne]

@pjcollins I've moved this to .NET 8, since I believe it's not required for .NET 7?

[rolfbjarne]

I'm adding a dependency on arcade here: #21469, which will pull all the arcade tools into the repo.

I'm not sure if anything else is needed?

[pjcollins]

This issue is pretty stale, we've effectively been on the latest publishing (darc/maestro) infra since commit 2abbaf9 and 2562461.

The next major step to becoming an "arcade" repo would be fully onboarding to the build infrastructure, and we could maybe rename this issue or resolve it and create a new one to track that effort.

@rmarinho has been wading into this migration process on the MAUI side and I think will be the best resources to help guide any next steps here. By my understanding, once arcade is added as a dependency you will then need to update the pipeline to use arcade build templates and scripts and set up an internal mirror for official builds.

[rolfbjarne]

Ok, that sounds like it's best done after we've moved into the dotnet org, so I think we can wait until then.