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.

Currently the teleportr database supports a LatestDeposit method,
which returns the highest block number observed, if any. The intent was
to use this as the starting point for syncing, however, this isn't super
useful as there may be long periods of inactivity that we have already
scanned.

Instead, we now store the last processed block in a separate table, and
pass the end of the ingestion block range as argument to UpsertDeposits.
The list of deposits and last processed block are written atomically to
avoid consistency issues. The value can be retrieved using the
LastProcessedBlock getter.

Less casting.

This avoids having l2geth as a dependency for other projects building on
bss-core. Speicifically this avoids having to copy l2geth into docker
builds.

feat: fix teleportr ci, and lint target

Also fixes a linter error that wasn't caught while the CI was broken.

Version Packages

Develop -> Master

l2geth: remove dead code

Some left over dead code is removed.
It has never been triggered and cannot
be triggered due to the locks in the syncservice.

l2geth: don't block read rpc when doing initial sync

l2geth: fix startup logic for repairing queue index

feat(dtl): hardcode bss hf1 index into the dtl

Hardcodes the index of the first BSS hardfork into the DTL, depending on
the chain ID. This is easier than asking users to set an environment
variable each time.

fix(rhc): dockerfile not properly including sdk