Transition Agent Pools from `Windows-2019TLS` -> `Windows-2022TLS`

In a bunch of our repositories, we have the following platform configs:

```
"windows-2019": { "OSVmImage": "MMS2019TKS", "Pool": "azsdk-pool-mms-win-2019-general" },
```

Needs to shift to be

```
"windows-2022": { "OSVmImage": "MMS2022TLS", "Pool": "azsdk-pool-mms-win-2022-general" },
```

However. However, before this happens, we need to move _some_ of the cores that we currently allocate to the `windows-2019` pool to a NEW pool for the 2022 machines. When that happens, we will need to PR the adjustments in each language repository to shift to consume that new pool.

This will be a balancing act, as as each repo transitions, the load on the previous pool will lighten commensurately.

- [ ] azure-sdk-for-java
- [ ] azure-sdk-for-net
- [ ] azure-sdk-for-js
- [ ] azure-sdk-for-python
- [ ] azure-sdk-for-go
- [ ] azure-sdk-for-cpp
- [ ] azure-sdk-for-c
- [ ] azure-sdk-for-ios
- [ ] azure-sdk-for-android