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.

chore(deps): bump follow-redirects from 1.14.7 to 1.14.8

Fix and usability improvements for L1 gas and cost estimates in L2Provider

packages/contracts: Add flag to automatically set ownership

Version Packages

Develop -> Master

dtl: Periodically log current l2 sync

teleportr: add TeleportrDeposit and TeleportrDisburser contracts

fix: add logging to the DTL when BSS HF1 is live

Adds a basic log line to the DTL when BSS HF1 is active. Will also log
when BSS HF1 is not active.

feat(sdk): add approval fns to the SDK

Description:

Instead of adding all the transaction fields, have serialize only add the fields we need.

This lets developers use the code pattern:

```js
const txReq = await greeter.populateTransaction.setGreeting(greeting)
const tx = await signer.populateTransaction(txReq)
provider.estimateL1Gas(tx)
```

Instead of the more error prone:

```js
const txReq = await greeter.populateTransaction.setGreeting(greeting)
const tx = await signer.populateTransaction(txReq)
delete tx.from
delete tx.chainId
provider.estimateL1Gas(tx)
```

This is a direct copy of the BridgeDeposit.sol contract apart from the
name change, some code moves to make the linter happy, and promoting
various public methods to external to satisfy slither.

fix: handle null response in `eth_getBlockRange`

feat: verify contracts on sourcify during deploy

fix(sdk): have sdk properly wait for transactions