build(deps-dev): bump @types/node from 20.10.1 to 20.10.2

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.10.1 to 20.10.2.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

contracts-bedrock: StandardBridge pausability

https://github.com/ethereum-optimism/optimism/pull/8377 is very
important because it would catch the regression of this not
being caught

Only impacts deposits

Enable extended pause functionality in the standard bridge.
Includes updates to tests and the deploy script.

feat(ctb): Refactor `SemverLock`

contracts-bedrock: cross domain messenger comment

Improve the comment to make it more accurate in the `L1CrossDomainMessenger`.

docs: Fix broken PR guideline hyperlink

op-node: Remove Panic while Span Batch Derivation

op-chain-ops: cleanup immutables

op-e2e: Improve e2e test for span batches

Co-authored-by: clabby <ben@clab.by>

We really only need to know if a contract has immutables and not what
the immmutables are to write good tests to ensure that all contracts
that have immutables are covered in the L2 genesis generation. Adding in
the actual immutables references as a string resulted in a lot of diffs
because the ast ids where used in them. This updates the bindings to use
a boolean instead of the string. Now we can still tell if a contract has
immutables and we dont care about what the offsets are. This will not
result in a large diff for the smart contracts when ast ids change.
It will only flip a bool when immutables are added or removed from a
contract.

feat(op-challenger): alphabet output bisection game

contracts-bedrock: include `initialize` checks for L2 contracts