l2geth: bring back unsupported RPC methods

Previously, any RPC methods involving hot keys and
signing by the node were disabled when the node
ran with the OVM configured. This was to prevent
users from attempting to use these methods against
the live sequencer. Now that the infrastructure is
more mature with `proxyd`, particular RPC requests
can be routed appropriately and blocked at the infra
level. Allowing these methods makes local development
easier.

This change cannot be adopted without coordination
from infra providers, ensuring that they will block
these methods at their infrastructure. Each optimism
node has at least 1 key that is used to ensure
block production is deterministic when running in
clique mode.

Also forward transactions to the sequencer when
running as the verifier for the RPC endpoint
`eth_sendTransaction`. This RPC utilizes a key
that the node is managing.

Version Packages

Develop -> Master PR

go/batch-submitter: HTTP/2 fixes

feat: modify txmgr to send EIP-1559 txns

test: improve test coverage for aliasing

l2geth: Add berlin hardfork

Develop -> Master PR

Removes the MAX_L1_GAS_PRICE_IN_GWEI and GAS_RETRY_INCREMENT env vars,
as well as the MinL1GasPrice, MaxL1GasPrice, and GasRetryIncrement
values from the txmgr config struct.

This commit adds a fallback in case the L1 provider does not support
queries for eth_maxPriorityFeePerGas. Of our infrastructure providers,
i.e. Alchemy, Infura, Quicknode, and Hardhat (in test envs), only
Alchemy suports this call. In production, we will be routing this call
directly to Alchemy, which should work in the general case. However, if
they were to be unavailable the batch submitter would be stalled until
service was restored. This modification also allows the new EIP-1559
batch submitter to pass our integration tests, since the default Hardhat
backend can't support the query either.

Version Packages

Develop -> Master PR

fix(bss): have BSS correctly create new contexts

Revert "l2geth: berlin hardfork"

l2geth: berlin hardfork

fix(sdk): clean up tx override api

Fixes a bug in the batch submitter where new contexts were not being
correctly created for L1 to L2 transactions with a different timestamp.
This bug exists because of recent changes to L2Geth where timestamps are
now being updated more frequently.

Slightly cleans up the API for overriding transaction options. Previous
API was a bit confusing and didn't leave room for additional optional
parameters. By separating options and overrides, we can add new options
that are unrelated to transaction overrides.

feat(sdk): implement withdrawETH

This commit implements the SDK's withdrawETH function which allows users
to withdraw an amount of ETH (specified in wei) from L2 to L1.

test/docs: Improve docstrings and tests for utils in hex-strings.ts

ci: decouple rpc-proxy publishing from l2geth

ci: update version of changesets

batch-submitter: import performance

feat(sdk): implement depositETH