When testing shard renames in magic restore, we check that metadata collections that refer to the old shard ID have correctly been updated to refer to the new shard name. However, these checks only look at known shard ID references that are modified in the restore procedure.

We need a way to catch any new sharding metadata referring to shard IDs. To do so, we should introduce a "shard ID consistency check" to the magic restore test utility file. A solution we brainstormed was to iterate through all documents in the config, admin, local databases that have some field name that match *shardId. We could also hardcode the fieldnames to look out for. Neither of these solutions are perfect, but they'll provide some guardrails until we come up with a better solution.