On fresh startup, the DTL attempts to make a range
query that is very large when the starting L1 block
height is not configured. It looks for ownership
transferred events on the address manager, the first
one to happen indicates that the address manager was
deployed at that height.

Now that we use the same address manager over time instead
of the old way of upgrading the system where we would
redeploy the address manager each time, we must pass
the L1 start height as a config option to the DTL,
otherwise it will attempt to sync old transactions
(from a previous regenesis).

This commit will reduce the range at which the DTL
will query for the events, as alchemy only supports
a range of 2000. This will make the search prohibitively
slow, but that is ok as the value ought to be configured
anyways.

This functionality is really only useful for ephemeral networks.

A new logline is added for convenience.

fix: replace OE with Optimism

feat: implement getMessageReceipt and tests

Create a setup script for the integration tests

Version Packages

Develop -> Master PR

fix: make CI correctly report linting errors

maintenance(message-relayer): remove unnecessary js runner script

fix: have SDK generate coverage reports

fix: update SDK readme to include warning

batch-submitter: Fix the numTxPerBatch metric

Add nightly deploys

Changes the `numTxPerBatch` metric to observe the actual number of elements inside `batchParams` rather than `endBlock - startBlock`.

Metadata:

- Fixes ENG-1807

feat(sdk): add tests for getTokenBridgeMessagesByAddress

Bwilson/l2geth exporter

go/batch-submitter: Fix metrics server

The metrics server wasn't running because of a space between the host and port.

- Deploys the nightly image after the build. We can use a `kubectl rollout restart` here because the nightly uses images of the form `image-name:nightly` and have `imagePullPolicy` set to `Always`. This forces Kubernetes to always re-pull images upon pod restart.
- Adds the go batch submitter to the list of images that get bulit by the nightly

Metadata:

- Fixes ENG-1661

ops/docker: Use old directory in packages dockerfile

`Dockerfile.packages` placed build artifacts in `/optimism`, whereas all of our other Dockerfiles place build artifactrs in `/opt/optimism`. As a result, downstream consumers of the packages Dockerfile cannot use images created by our other Dockerfiles. This is a problem for the nightly environment, since it relies upon the `/opt/optimism` structure to customize container entrypoints.

This PR fixes the problem by having `Dockerfile.packages` put build artifacts in `/opt/optimism` like everything else.

Develop -> Master

Version Packages

feat: tests for CrossChainProvider constructor and getMessagesByTransaction