During the magic restore process, the server is in a restore state, and we may want to branch behavior based on this. For older manual restores, we check this state based on the shouldRecoverFromOplogAsStandalone function. For example, we'll check this function to determine if we should relax index constraints.

We should audit calls of this function throughout the codebase, examine what behavior we're changing based on if we're in a restore state. If the restore behavior is relevant to magic restore, we should also add a check for `storageGlobalParams.magicRestore`.

For context, this came out of a passthrough failure where a PIT magic restore process was applying a createIndexes oplog entry, and hit this invariant, because we were not relaxing index constraints during magic restore.