`op-deployer inspect` needs to run standard checks

op-deployer generates SCR files and runs checks for new chains. It looks like these chains are (at least by default) non-standard, non-standard candidate chains: the [default standard candidate flag is false](https://github.com/ethereum-optimism/optimism/blob/develop/op-deployer/pkg/deployer/inspect/superchain_registry.go#L41).

But op-deployer is often used to deploy both standard candidates and fully standard chains. We need an easy way to make sure that these chains are fully validated with `op-deployer inspect` (the command that chain deployers run to confirm that a chain has been correctly deployed).

We should probably make the standard checks the default, with an option to run only frontier or standard candidate checks instead.

This might mean one of the following approaches:

* Adding a non-standard flag to the `op-deployer inspect` subcommand
* Adding an option for frontier/standard candidate flags to the intents files consumed by op-deployer

Start with the op-deployer inspect subcommand and pkg/deployer/inspect/superchain_registry.go, especially the default standard candidate flag referenced in the issue. Compare that behavior with the intents files consumed by op-deployer and determine how standard, frontier, and standard candidate checks should be selected. Done means inspect validates fully standard chains by default while retaining an explicit way to run the other check modes.

Written by the indexing model from the issue text.