which fixes https://github.com/sc-forks/solidity-coverage/issues/652

Can bring up the system without needing to build locally
using the following command:

```
$ docker-compose -f docker-compose-nobuild.yml up
```

Simply clean up the `time.Ticker`s using `defer t.Close()`.
Not having this code should not cause any problems, but
it is best practice to close the tickers as not doing so
can result in memory leaks in certain cases.

Prevent the error being returned in consensus for when
the user does not have enough balance. The policy level
check *must* filter out transactions that do not have
enough gas to pay for their execution. The policy
level check happens in the `SyncService`. This change
gracefully handles the race condition where a user transaction
passes the policy level check as a `gas-oracle` transaction
is executing and updating the gas prices. If the gas price
goes up and the user transaction no longer can afford execution,
then it will return an error from consensus.

Adds the config option `DATA_TRANSPORT_LAYER_STARTING_L1_BLOCK_NUMBER`
or `--starting-l1-blocknumber` that allows for the user to specify
the L1 blocknumber to begin syncing from. This prevents users from
syncing old batches from a previous regenesis.

Rather than adding additional config args to npx hardhat deploy

Reasoning:
1. It manages the address manager
2. AddressSetter is overly generic

Discrete deploy scripts are prefixed with multiples of 10, allowing for related scripts
to be place between them without renaming all subsquent scripts