New Release tictoc

The following are the steps that need to be taken as part of a new release of .NET Aspire.

Things to do before release day

Share steps with validation team on how to acquire the release candidate.
Define who is writing the blog post for the announcement.
Ensure the blog post author checks with area owners for features that should be mentioned.
Start the process of updating the API Docs by using this template
Ensure all features have been signed off in all compliance aspects (privacy, globalization, security, accessibility)

Generate NuGet API Tokens
Ship packages to NuGet
- ServiceDiscovery packages should be shipped with the dotnetframework NuGet org
- Aspire.* packages should be shipped with the Aspire org token
Submit a PR to update our supported policy to the website repo
Submit a PR to update the templates in the relevant Visual Studio versions
Submit a PR in the dotnet-docker repo to update the dashboard Docker image.
Ship Blog Post
Ship Api Docs
Merge changes from internal branch (if applicable) and tag the release commit.
Create a new GitHub release based on that tag.
Create a PR to update our https://github.com/dotnet/aspire-samples and https://github.com/dotnet/eshop repositories
Push all packages to our public dotnet-public repo by queuing a build from this pipeline
Send a PR into main branch to update Package Validation version to match the published version