Validate known packed storage addresses

[mds1]

What

PR #1450 added storageCodeExceptions to silence false positives when a storage write contains a packed address. That worked, but it did so by skipping validation entirely for an (account, slot) pair — which also skips checking the address packed into that slot. This PR replaces that escape hatch with a check that actually validates the packed address.

Why

Some L1 upgradeable contracts pack an address alongside smaller fields in the same 32-byte slot (e.g. SystemConfig slot 108 packs superchainConfig with minBaseFee). The state-diff check reads the full 32-byte word, so the packed value is too large to look like an address and the embedded address slips past the normal code/EOA validation. We still want that address checked, not skipped.

How

1. Revert the config-driven storageCodeExceptions escape hatch.
2. Hardcode the known packed slots from the checked-in contracts-bedrock storage layout snapshots, which are the source of truth for the offsets.
3. For those slots, extract the packed 20-byte address and run the existing code/EOA validation on it. The match is keyed on both the slot number and the account's registry name (e.g. SystemConfigProxy), so an unrelated contract that happens to write the same slot number is left alone.
4. Leave every other storage write on the existing full-word validation path.

Slots covered: AnchorStateRegistryProxy / EthLockboxProxy / SuperchainConfig at slot 0, OptimismPortalProxy.superchainConfig at slot 53, OptimismPortalProxy.ethLockbox at slot 63, and SystemConfigProxy.superchainConfig at slot 108.