SERVER-89285 recently introduced a local catalog view reload in one of the ReplicaSetAwareService::onInitialDataAvailable hooks. However, other onInitialDataAvailable hooks might depend on the the local catalog being already reloaded (e.g. ShardingRecoveryService), but there is no ordering enforcement in how we call the hooks of each registered ReplicaSetAwareService.

We should audit if this is an actual issue, and also implement a mechanism to prevent this kind of dependency issues being inadvertently introduced in the future.

We should also check if there might be other dependencies between hooks other than the local catalog.