The authoritative DropCollection and DropDatabase DDL commands do not clean up config.cache.collections and config.cache.chunks.* entries, unlike their non-authoritative counterparts. This is intentional, as the authoritative CRUD path does not use these collections, so they are not expected to exist after a drop.

However, since not all DDLs are authoritative yet, the non-authoritative CRUD recovery path may still recreate these collections, leaving stale entries that the authoritative drop commands never clean up. This forces jstests/sharding/drop_collection.js to skip cached metadata validation when ShardAuthoritativeCollMetadata is enabled.

Once all DDLs are fully authoritative, remove the conditional escape in jstests/sharding/drop_collection.js.