[wiki migration] Release team pages (#148723)

This sorts the wiki pages owned by the Release team in the docs/ directory as planned in [flutter.dev/go/migrate-flutter-wiki-spreadsheet](https://docs.google.com/spreadsheets/d/1x65189ZBdNiLRygpUYoU08pwvXD4M-Z157c6pm8deGI/edit?usp=sharing) 

It also adds the release related labels to the bot for future PRs.

Changes to the content were only updating cross links. The remaining wiki links will be updated after the rest of the pages are relocated, the original wiki links still work in the meantime.

Part of flutter/flutter#145009

Author: Piinks

.github/labeler.yml

@@ -152,12 +152,16 @@ team-ecosystem:
   - changed-files:
     - any-glob-to-any-file:
       - docs/ecosystem/**/*
-
 team-engine:
   - changed-files:
     - any-glob-to-any-file:
       - docs/engine/**/*
 
+team-release:
+  - changed-files:
+    - any-glob-to-any-file:
+      - docs/releases/**/*
+
 tool:
   - changed-files:
     - any-glob-to-any-file:

docs/unsorted_wiki/Bad-Builds.md docs/releases/Bad-Builds.mddocs/unsorted_wiki/Bad-Builds.md renamed to docs/releases/Bad-Builds.md

@@ -23,7 +23,7 @@ refer to the FAQ section below
 ## Frequently asked questions
 
 ### How do I request a cherry-pick?
-To request a cherry-pick, utilize the [issue template](https://github.com/flutter/flutter/issues/new?assignees=&labels=cp%3A+review&template=7_cherry_pick.yml&title=%5BCP%5D+%3Ctitle%3E).
+To request a cherry-pick, utilize the [issue template](https://github.com/flutter/flutter/issues/new?template=7_cherry_pick.yml).
 
 ### Who can request a cherry-pick?
 
@@ -41,7 +41,7 @@ The release engineering team will assign a cherry-pick reviewer who is an expert
 ### Lifecycle of a cherry-pick
 
 1. The cherry-pick requester opens a cherry-pick pull request to the [beta](https://github.com/flutter/flutter/blob/beta/bin/internal/release-candidate-branch.version) or [stable](https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version) **candidate** branch (follow the respective link to find the branch name)
-2. A cherry-pick issue is filled out completely and created utilizing the [cherry-pick template](https://github.com/flutter/flutter/issues/new?assignees=&labels=cp%3A+review&template=7_cherry_pick.yml&title=%5BCP%5D+%3Ctitle%3E) in the [flutter/flutter](https://github.com/flutter/flutter) repository.
+2. A cherry-pick issue is filled out completely and created utilizing the [cherry-pick template](https://github.com/flutter/flutter/issues/new?template=7_cherry_pick.yml) in the [flutter/flutter](https://github.com/flutter/flutter) repository.
 3. The release engineering team is notified that a cherry-pick request is in queue and assigns an appropriate reviewer who is an expert in the area who will review the cherry-pick issue and associated cherry-pick pull request.
 4. The release engineering team applies the `merge-to-beta` or `merge-to-stable` label.
 5. The cherry-pick request then enters one of the following states.

…orted_wiki/Flutter-Cherrypick-Process.md …s/releases/Flutter-Cherrypick-Process.mddocs/unsorted_wiki/Flutter-Cherrypick-Process.md renamed to docs/releases/Flutter-Cherrypick-Process.md docs/unsorted_wiki/Flutter-Cherrypick-Process.md renamed to docs/releases/Flutter-Cherrypick-Process.md

@@ -5,7 +5,7 @@ Flutter has the following channels, in increasing order of stability.
 ### `master` (aka `main`)
 
 The current tip-of-tree, absolute latest cutting edge build. Usually functional, though sometimes we accidentally break things. We do not run the entirety of our testing before allowing patches to land on this branch. We do not
-recommend using this branch unless [you are contributing to Flutter](https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md).
+recommend using this branch unless [you are contributing to Flutter](https://github.com/flutter/flutter/blob/main/CONTRIBUTING.md).
 
 The API documentation for the most recent commit on `master` is staged at: <https://master-api.flutter.dev>
 
@@ -58,6 +58,6 @@ If you really need a particular patch and it's a fix to the flutter/flutter repo
 
 ## See also
 
-* [[Release process]], which describes the details for how we push builds from channel to channel.
+* [Release process](Release-process.md), which describes the details for how we push builds from channel to channel.
 * [Cherrypick process](https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process), where we cover how to request an issue for cherrypicking.
 * [Release notes](https://flutter.dev/docs/development/tools/sdk/release-notes), where we document changes to each version of the stable channel.

…d_wiki/Flutter-build-release-channels.md …leases/Flutter-build-release-channels.mddocs/unsorted_wiki/Flutter-build-release-channels.md renamed to docs/releases/Flutter-build-release-channels.md docs/unsorted_wiki/Flutter-build-release-channels.md renamed to docs/releases/Flutter-build-release-channels.md

@@ -2,7 +2,7 @@ With each beta we need to test that there are no regressions. We have lots of au
 
 ## When to test betas
 
-We announce betas on our Discord (see the [[Chat]] page for the invite link), in the #releases channel, about once a month.
+We announce betas on our Discord (see the [Chat](https://github.com/flutter/flutter/wiki/Chat) page for the invite link), in the #releases channel, about once a month.
 
 ## How to get a beta build
 

…i/Hotfix-Documentation-Best-Practices.md …s/Hotfix-Documentation-Best-Practices.mddocs/unsorted_wiki/Hotfix-Documentation-Best-Practices.md renamed to docs/releases/Hotfix-Documentation-Best-Practices.md docs/unsorted_wiki/Hotfix-Documentation-Best-Practices.md renamed to docs/releases/Hotfix-Documentation-Best-Practices.md

@@ -21,7 +21,7 @@ At the start of every month, Flutter aims to ship a new beta to users. We prefer
 
 ## Conducting releases
 
-[Conductor](https://github.com/flutter/flutter/tree/master/dev/conductor) is a release tool written in Dart to drive Flutter releases. It's the source of truth for what's needed to ship a release. Generally, it can promote candidate branches to betas, betas to stable, and hotfix releases. It handles the nuances of git, such as pushes, cherrypicks, and tagging, and the complexities of Flutter, such as rolling and release infra.
+[Conductor](https://github.com/flutter/flutter/tree/main/dev/conductor) is a release tool written in Dart to drive Flutter releases. It's the source of truth for what's needed to ship a release. Generally, it can promote candidate branches to betas, betas to stable, and hotfix releases. It handles the nuances of git, such as pushes, cherrypicks, and tagging, and the complexities of Flutter, such as rolling and release infra.
 
 A Flutter release is very similar to what would be seen on the master branch, with some exceptions:
 1. Ensure all builds and tests are green
@@ -73,9 +73,9 @@ Since `stable` and `beta` are branches, new Y releases require a force push. Thi
 
 ## See also
 
-- [[Cherrypicks|Flutter Cherrypick Process]]
-- [[Quality Assurance]]
-- [[Release channels|Flutter build release channels]]
-- [[Release versioning]]
+- [Flutter Cherrypick Process](Flutter-Cherrypick-Process.md)
+- [Quality Assurance](Quality-Assurance.md)
+- [Flutter build release channels](Flutter-build-release-channels.md)
+- [Release versioning](Release-versioning.md)
 - [SDK Releases](https://docs.flutter.dev/development/tools/sdk/releases?tab=linux)
-- [[Where's my Commit?]]
+- [Where's my Commit?](Where's-my-commit.md)