As SERVER-97891 introduces a new durable shard-local collection called `config.shard.databases`, we need to examine how the magic restore procedure will interact with this collection.

The purpose of this ticket is to track the necessary changes to ensure that the magic restore procedure does not miss or restore the new collection `config.shard.databases` in an inconsistent state. This collection is crucial as it contains the authoritative database metadata for the shard.