[wiki migration] Tool team pages (#148779)

This puts the wiki pages owned by the Tool team into the docs/tool 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 tool team labels to the label bot for future PRs.

Changes to the content were only updating cross links, or link to refer to the main branch rather than master.
Remaining links to the wiki will be updated once all other pages have finished moving, they still work in the meantime.

Part of https://github.com/flutter/flutter/issues/145009

docs/infra/Updating-dependencies-in-Flutter.md

@@ -0,0 +1,21 @@
+Instead of manually updating dependencies in a `pubspec.yaml` file, use the [`update-packages`](packages/flutter_tools/lib/src/commands/update_packages.dart) CLI tool:
+
+## To update all dependencies:
+
+`flutter update-packages --force-upgrade`
+
+## To pin a dependency:
+
+Sometimes you need to prevent a dependency from being updated when you run `flutter update-packages --force-upgrade`.
+
+In that case, first pin the dependency in [`kManuallyPinnedDependencies`](https://github.com/flutter/flutter/blob/5bd34ef541575eddae6aaa82fc76a59ae7e464c3/packages/flutter_tools/lib/src/update_packages_pins.dart#L17) and a include a comment with a link to an issue to unpin the dependency.
+
+You can then re-run `flutter update-packages --force-upgrade`.
+
+## To update a single dependency for cherrypicks:
+
+Sometimes you need to update a single dependency as a [cherrypick to a release candidate branch](https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process).
+
+In that case, you can run:
+
+`flutter update-packages --cherry-pick-package=[pub package name] --cherry-pick-version='[pub package version]'`