refactor: decouple AnchorStateRegistry from SystemConfig, use SuperchainConfig instead

[GarmashAlex]

Description

This PR refactors the AnchorStateRegistry contract to remove its dependency on SystemConfig and instead use SuperchainConfig and ETHLockbox for chain-wide configuration and pause logic. The initialize function and related interfaces have been updated to accept ISuperchainConfig and IETHLockbox instead of ISystemConfig. All logic related to pausing and guardian checks now references SuperchainConfig. Deployment scripts, contract manager logic, and tests have been updated accordingly.
This change is required to support interop mode, where AnchorStateRegistry is shared across multiple chains, but SystemConfig remains chain-specific.

Tests

• Updated all existing tests for AnchorStateRegistry to use the new constructor and interface.
• Verified that pause and guardian logic now reference SuperchainConfig as intended.
• All relevant deployment and migration scripts have been updated and checked for compatibility.

Additional context

This refactor is necessary to decouple AnchorStateRegistry from chain-specific configuration, ensuring it can be safely used in interop scenarios across multiple chains.
No new features are introduced; this is a structural and architectural improvement to support future multi-chain deployments.

Metadata

Closes #16114

[smartcontracts]

Hi - changes to smart contracts need to go through a design review and specs process. This implementation is also not entirely correct as it doesn't account for changes to the ETHLockbox contract, which is why the SystemConfig is valuable. For now I'm going to mark this PR as do-not-merge and I'll investigate to see if we'd accept a PR for this.