Update docs after #165258 (#165716)

Follow up from #165258 
Removes references to the deleted Infra-Ticket-Queue.md, and mentions of
the Infra Ticket Queue Github project.
Not sure if we should keep the issue template?

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

dev/bots/README.md

@@ -5,9 +5,8 @@ This directory exists to support building Flutter on our build infrastructure.
 Flutter build results are available at: <https://flutter-dashboard.appspot.com>.
 
 Flutter infra requires special permissions to retrigger builds on the
-[build dashboard](https://flutter-dashboard.appspot.com/#/build). File an
-[infra ticket](../../docs/infra/Infra-Ticket-Queue.md) to
-request permission.
+[build dashboard](https://flutter-dashboard.appspot.com/#/build). File a `team-infra`
+issue to request permission.
 
 The [LUCI](https://chromium.googlesource.com/infra/luci/luci-py/+/refs/heads/main/README.md)-based
 bots run the [`test.dart`](test.dart) script for each PR and submission. This
@@ -26,8 +25,7 @@ The build dashboard includes post-commit testing run on physical devices. See
 
 A [set of infra scripts](https://flutter.googlesource.com/recipes/)
 run on Windows, Linux, and Mac machines. The configuration for how many
-machines and what kind are managed internally by Google. File an
-[infra ticket](../../docs/infra/Infra-Ticket-Queue.md)
+machines and what kind are managed internally by Google. File a `team-infra` issue
 to request new machine types to be added. Both of these technologies are highly
 specific to the [LUCI](https://github.com/luci) project, which is the successor
 to Chromium's infra and the foundation to Flutter's infrastructure.

dev/devicelab/README.md

@@ -240,8 +240,8 @@ target for each operating system.
 
 ## Adding tests to presubmit
 
-Flutter's DeviceLab has a limited capacity in presubmit. File an infra ticket
-to investigate feasibility of adding a test to presubmit.
+Flutter's DeviceLab has a limited capacity in presubmit. File a `team-infra`
+issue to investigate feasibility of adding a test to presubmit.
 
 ## Migrating to build and test model