For rpc-proxy and proxyd. Just a patch changeset to trigger
releases as a bug prevented releases previously.

The variables used in the canary release were used in the actual
release, causing it to not have the correct variables in place.
This caused the CI to skip the steps for publishing the `rpc-proxy`
and `proxyd`. This commit should fix the problem.

Version Packages

Develop -> Master

Add CORS support to the proxy

workflows: fix build-args syntax

The docs specify that `build-args` for the Github action
`docker/build-push-action@v2` should be a list, but
doing so results in an error:

`The workflow is not valid. .github/workflows/release.yml (Line: 362,
Col: 13): A sequence was not expected`

This updates the syntax to copy the example here:
https://github.com/docker/build-push-action/blob/3c507bedc4de3249e107413a7358ae1af558fd79/UPGRADE.md#L68

Uncertain if the env var parsing will work with this syntax

Develop -> Master PR

Bypass lua checking when the request is not a POST

Fixed nit, added changeset for rpc-proxy

Add proxy RPC daemon

feat: add batch-submitter/txmgr for tx publication and  gas bumping

This commit adds a SimpleTxManager for tracking and bumping fees on txs
the batch submitter needs to publish. The bulk of the logic is adapated
from the existing tx manager (YNATM) used in the typescript version to
minimize any new classes of bugs that are not already considered.

The manager is configured via a min and max gas price, as well as an
additive gas price step that is applied after each resubmission interval
elapses, before signing and broadcasting a new transaction. This
corresponds to the LINEAR fee policy available in YNATM.

Txs generated from the same call to Send are treated as equivalent, thus
the method blocks until the first tx confirms. Care is taken to
throughly unit test the interactions and edge cases, as subtle bugs in
tx publication can lead to big headaches in prod. To this end, we
achieve 100% test coverage in the txmgr package:

```
coverage: 100.0% of statements
ok  	github.com/ethereum-optimism/go/batch-submitter/txmgr	10.311s
```

core-utils: parse L1 timestamp in injectContext

Also parse the L1 timestamp in `injectContext`.
This value is useful but was not previously parsed
and added to the ethers provider

The constants are actually defined in the reverse order of their
severity. The prior behavior would log everything _but_ log.LvlCrit.

feat: batch-submitter peripheral resources

Adds the main BatchSubmitter service struct that will provide resources
to the (yet to be implemented) TxBatchSubmitter and StateBatchSubmitter
sub-services. This root service also sets up Sentry logging and
the embedded Prometheus metrics server.

Adds logic to parse private key strings from a string (for debug
purposes) or from a valid BIP39 mnemonic and valid BIP32 derivation
path.

Additionally adds a ParseAddress helper to ensure proper parsing and
sanitization of contract addresses.

Creates a custom SentryStremHandler that functions analgously to a
log.StreamHandler, with the exception that any LvlError logs or higher
are posted to Sentry. It also leverages the existing go-ethereum logging
formatters, specifically JSONFormat, to post any additional log context
items as a JSON blob via extra data.

build: fix mismatched js package versions (reduce yarn.lock size)

feat: add go/batch-submitter env var parsing

fix: linting

fix(contracts): Update yarn.lock

Introduce Docker layer caching

Co-authored-by: Liam Horne <liam@lihorne.com>