In order to ensure that removing entries from config.cache.collections cannot result in us treating a collection as unsharded when it is actually sharded, we would like to create a passthrough suite which mimics the behavior of a common remediation technique in which we remove an entry from config.cache.collections.

We may not want to commit this, but we should at least create and run the suite to see if there are any problems we are unaware of.

We expect that we will hit this assertion, so in the suite we will need to demote it to a uassert and probably add retries for this error in the catalog cache (we are okay with bubbling this up to users during the remediation, but it will likely cause some tests to fail.