[Tracking] Release Tooling

[JReinhold]

Tracking progress for the implementation of #22182

Tasks

Preview Give feedback

1. Bring back prototype repo to a pristine state without Changesets
2. Build version script that bumps versions everywhere Versioning script monorepo-release-tooling-prototype#17
3. Release Tooling Project: Build write-changelog script that writes a changelog based on GitHub PR information #22611
   +0
   
4. Release Tooling Project: Build generate-pr-description script that generates a PR description for a Release PR #22601
   +0
   
5. Release Tooling Project: Build pick-patches script that cherry picks patches back to main #22603
   +0
   
6. Release Tooling Project: Build publish script that publishes new versions #22604
   +0
   
7. Release Tooling Project: Build check-release-needed script that checks if a release is needed or not #22610
   +0
   
8. Release Tooling Project: Build GH Action that creates/updates a Preelease PR #22605
   +0
   
9. Release Tooling Project: Build GH Action that creates/updates a Patch Release PR #22606
   +0
   
10. Release Tooling Project: Build GH Action that publishes new prereleases #22607
    +0
    
11. Release Tooling Project: Build GH Action that publishes new patch releases #22608
    +0
    
12. Create a video tour of the workflow from A-Z that clearly demonstrates how we work with it, to gather feedback on if we want to change the main workflow
13. Release Tooling Project: Enforce good PR titles #22837
    +0
14. Change branches from "main-v2-release" and "next-v2-release" to "release/next" and "release/main"
15. Release Tooling Project: Support canary releases for PRs #22840
    +0
16. Fail release PR until all checks are complete
17. Release Tooling Project: Document flow in contribution guidelines #22609
    +0
    
18. Handle when next gets new changes while release is ongoing. Probably tag the versioning commit and not the merge one

Migrating prototype to monorepo

Preview Give feedback

1. Add scripts, dependencies and Actions and anything else necessary to the monorepo with a PR to next. Release: New release tooling #22959
2. Figure out what handle-release-branches.yml does
3. Add secrets and environments via the GH UI
4. Merge to next and hopefully see the "Version Packages" PR
5. Merge the "Version Packages" PR and hopefully trigger a new 7.1.0-alpha version release
6. Ensure monitoring, status page and scheduled CI still works with the branches

Follow up tasks

Preview Give feedback

1. [Bug]: New release flow doesn't update versions on docs site #23000
   build +1
   
2. Changes to CHANGELOG.md will only happen on main, should be changed on next as well
3. Simplify PR list in description - remove 3 todos per PR
4. Add information to PR list about which PRs are also patching
5. Sort PRs by importance (to-be-released at the top)
6. Remove all the deprecated bits that aren't necessary for releases anymore.
7. Cherry picks can also fail with "empty commit" message if it has already been picked, in which case it shouldn't cause a "manual cherry pick needed" message
8. Change Release PR titles to "Release: <Type> [ID] <next-version>", eg: "Release: Prerelease beta 7.1.0-beta.0