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

Also perform validation to prevent passing arguments which conflict, ie. arguments
for upgrades vs. arguments for fresh deployments.

Also introduces a new function getLibAddressManager() which returns the
address based either on config or previous deployment.
Also remove renames deployAndRegister to deployAndPostAction, and modifies
its behavior accordingly.

There was a bug in the config, the `file`
was not relative to the `context`

Fixes a typo in the CI so that the `hardhat-node` docker
image is correctly published.

The ChainStorageContainer-CTC-queue contract was removed from the
CTC in a previous commit. This commit removes some code that was
no longer necessary as a result of that change, including the
deployment script.

Signed-off-by: kf <kelvin@optimism.io>

Update the SCC being used on kovan with a 10 second
fraud proof window. This makes testing withdrawals very
easy.

Publishing the `hardhat-node` docker image will make using
the `docker-compose` setup much easier for developers
as they will be able to pull all of the docker images needed.
There is an existing `ethereumoptimism/hardhat` image that is
on an older version of `hardhat` that was pushed by the old
Optimism monorepo. This version of hardhat does not support
EIP1559 so it is expected that it will not work with the
existing tech stack.

This PR adds the ability to publish the `hardhat-node` docker
image for both releases and canary releases. A following PR
will be introduced that updates the `docker-compose` files
to specifically reference the new `hardhat-node` image
such that there will not be name collision errors in the future.

Previously, the builder would not be published with
a tag, meaning that any time that the canary build
was triggered, it would publish `ethereumoptimism/builder:latest`.
This clobbers the release from `master` which may have downstream
effects.

Allows for custom builder tags to be used

Previously, the `latest` tag would be implicitly
always used for the `builder`. This introduces
the ability to introduce a custom tag name when
building images that bulid `FROM` the `builder`.

Update the batch validation config parsing so
that the tx batch validation is false by default.
This means that to enable transaction batch validation,
the env var `VALIDATE_TX_BATCH` must be explicitly set
to `true`. If it is not set, then it will default to false.
The logic is shown below for the implementation.

```js
> '' ? '' === 'true' : false
false
> 'false' ? 'false' === 'true' : false
false
> 'true' ? 'true' === 'true' : false
true
```

It can be used with the command:

```
$ npx hardhat deploy --tags hardhat --network fork --fork-network kovan
```

A new parameter `--fork-network` is added which specifies the network
that is being forked. We cannot use the actual network due to it
checking the `.chainId` file in the `deployments/xxx/` directory
and comparing that against the remote network.

It is hidden behind the `hardhat` tag and only runs if the deploy config
has the network set to `fork` with `--network fork`. It is up to the
user to configure `hardhat node` with the correct fork url.

This should be used with the env vars:
```
CONTRACTS_TARGET_NETWORK=fork
CONTRACTS_DEPLOYER_KEY=0x...
CONTRACTS_RPC_URL=<url of forked network>
```

This must run first and I didn't want to rename all of the files,
so I named it with the prefix `0000`.