Removes yargs as a dependency from the contracts package since it wasn't
being used. Always good to cut unused dependencies.

fix(bridge): Corrected a comment

fix(rhc): fix dockerfile bug

contracts: fetch batches hardhat task

increase coverage of contracts package

This commit increases the statement and branch coverage of the contracts
package. More specificall the contracts that were covered are:

- AddressDictator
- ChugSplashDictator
- L1CrossDomainMessenger
- L1StandardBridge
- CanonicalTransactionChain
- ChainStorageContainer
- StateCommitmentChain
- L2CrossDomainMessenger
- L2StandardBridge
- WETH9
- Lib_OVMCode
- Lib_RLPWriter
- Lib_SecureMerkleTrie
- Lib_Buffer
- Lib_MerkleTree

Allows for easy serialization and display in frontends
or for data collection

Adds a hardhat task to fetch batches. Logs are written
to stderr so that the stdout can be written to a file
or passed to `jq`.

```bash
export CONTRACTS_TARGET_NETWORK=...
export CONTRACTS_DEPLOYER_KEY=...
export CONTRACTS_RPC_URL=...
npx hardhat fetch-batches --network main --start 14311261
```

integration-tests: Fix merge issue

readme: update docs around doing releases

Remove unnecessary contract references in integration-tests

feat: always run go unit tests/golangci-lint on every PR

feat: typed batches and batch compression

added internal/external import seperation on integration tests

The current methodology only attempts to run unit tests when changes to
the package paths are detected. However, this is brittle and most
notably doesn't capture when changes are made to the workflow itself. As
a result, a green build in a PR doesn't neccessarily correlate to a
green build after merge. Unit tests are cheap, so this should prevent
needless false positives.

ci: Update nightly address manager addr, notify on itest failures

feat: add Teleportr service

This commit updates the config so that the CI can run
the batch submitters in each mode so that we continue
to test each of the batch types.

It also lints the yaml files

Update the docker compose config such that the
batch submitters submit type 0 batches (zlib compressed)
and then add an integration test for that functionality.

Allow the go batch submitter to submit typed batches.
The env var `BATCH_SUBMITTER_SEQUENCER_BATCH_TYPE=zlib`
can be set to enable the submission of zlib compressed
batches. If that env var is not set, then legacy batches
will be submitted instead.

The data transport layer will now be able to index
typed batches. A typed batch has the first batch context
have a timestamp of 0 and the blocknumber is used as an
enum to determine the type of the batch.

It is not possible to have a timestamp of 0 in realistic
conditions. Batches that have a non zero timestamp
as the first batch context are considered a legacy batch.

The first typed batch is type 0 where the blocknumber is 0
and the transaction data is compressed with zlib.

Enable typed batch support in the batch submitter.
Type 0 batches (zlib compressed) can be enabled with
the env var `BATCH_SUBMITTER_SEQUENCER_BATCH_TYPE=zlib`
or via the flag `--sequencer-batch-type zlib`.

Update the batch serialization to allow for typed batches.
Also include logic for type 0 batches, which are compressed
with zlib.