Context
SPM-4330 has introduced the deployment of multiple mongos in several suites.
Every mongos has its own Mongo connection and they are managed by the multi-router

Problem
Since then, the test find_after_coll_drop.js  will consistently fail here 
with error

 Error: Unable to find key ID 11d58b8a-0c6c-4d69-a0bd-70c6d9befae9 from findAfterCollDropDB.keystore on node localhost:20004 : 

The key 11d58b8a-0c6c-4d69-a0bd-70c6d9befae9 is hard-coded by the test but it's not present in the keyvault when specified by the caller.

With a single mongos, the driver seem to rely on cached schema , which is retrieved via listCollections in case that cache is empty

• In case of "warm" mongo connection (i.e the same mongo that created the previous collection) the schema will own latest key in the keyvault
• In case of stale mongo connection, the system fetch the hard-coded key which won't be found in the key-vault and refuse the serve any request.

The cache seems to refresh every minute which might make this issue not necessarily critical

Given my limited understanding of the infrastructure, I will let the team understanding if this is an actual issue

Repro
1. Remove the flag 
2. Execute

python ./build/install/bin/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=0.5 --mongodSetParameters={logComponentVerbosity: {verbosity: 0}} --mongosSetParameters={logComponentVerbosity: {verbosity: 0}} --jobs=1 --log=file --suite=sharding_jscore_passthrough src/mongo/db/modules/enterprise/jstests/fle2/query/find_after_coll_drop.js --repeatTests 3 

creates and drops an encrypted collection with the purpose of