There are a number of tests that fail when run against a sharded cluster with two mongos routers and default configurations.

The main cause of failure is that a sharded cluster started by mlaunch uses consecutive port numbers. Notice in particular (below) that the cluster is using port 27020. This conflicts with `mongocrypt` also defaulting to use port 27020.

While mlaunch can be told to use a different port range, that then in turn requires temporarily setting up the `MONGODB_URI` and `MONGODB_URI_WITH_MULTIPLE_MONGOSES` which requires a number of manual steps to set, load, unset and unload. The preferred scenario is that the tests should all pass using a default mlaunch sharded cluster configuration and the default connection strings built into the test suite.

To reproduce start a cluster with mlaunch like this:

mlaunch init --sharded 1 --replicaset --nodes 1 --mongos 2 --binarypath C:\mongodb\v5.0.3\bin --setParameter enableTestCommands=true 

which results in the following cluster configuration:

PS C:\mlaunch\v5.0.3\sharded> mlaunch list

PROCESS          PORT     STATUS     PID

mongos           27017    running    16132
mongos           27018    running    3660

config server    27020    running    27964

shard01
    mongod       27019    running    26732


PS C:\mlaunch\v5.0.3\sharded>

 Then run the tests using:

.\build.ps1 --target=testnet472 // or test 

The tests should be run using the default connection strings built into the test suite. In other words, the `MONGODB_URI` and `MONGODB_URI_WITH_MULTIPLE_MONGOSES` environment variables should not be set.