contracts-bedrock: modularize build

Modularize the build of `contracts-bedrock` so that
more packages can be dev deps. Make it so that the differential
testing build is different than the typescript build.

This is part of the larger sdk integration work, split out
into its own smaller PR.

contracts-bedrock: fix typechain export

This was being incorrectly set in the rollup json relative to the
HD path supplied to the batcher was. This resulted in L2 reorgs
on the sequencer & the inability to send L2 transactions.
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

contracts-bedrock: update hardhat-forge plugin

Updates the hh forge plugin to the following:

```
"@foundry-rs/hardhat-forge": "^0.1.16"
```

Includes bugfixes for when multiple imports
of contracts with the same name happens.

contracts-bedrock: update hardhat forge dep

The `package.json` defines the files that are included
in the `npm` package, the previous glob did not match
all of the typechain artifacts.

ci: remove publishing of deprecated images

op-bindings: speed up build

* contracts-bedrock: fix build

Standardize on the upgradable initializable since the contracts
are technically upgradable it is more clear. There are no real
implementation differences between the upgradable and standard
initializable implementations. `OwnableUpgradable` is `initializable`
imported from the upgradable package, and the `L2OutputOracle`
inherits from `OwnableUpgradable`. This means that the only
way to standardize on a single implementation of `Initializable`
is to use the upgradable version.

This also bumps the version of the openzeppelin contracts
dependency because they refactored the initializable implementation
and made it easier to understand.

https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/releases/tag/v4.7.0
https://github.com/OpenZeppelin/openzeppelin-contracts/pull/3450

* op-bindings: regenerate

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Use only 1 initializable instead of two different initializable
imports. Using contracts with the same name will break hardhat.

The two different initializable imports were:

```solidity
import { Initializable } from "@openzeppelin/contracts-upgradeable/proxy/utils/Initializable.sol";
```

```solidity
import { Initializable } from "@openzeppelin/contracts/proxy/utils/Initializable.sol";
```

This standardizes on not using `contracts-upgradeable`.

The `js-builder` and `go-builder` are no longer
used, they were replaced by `ci-builder`. Their
dockerfiles have already been deleted from the
repo, this now deletes their reference in the CI
docker build pipeline.

contracts: update docs

Due to a new version of the openzeppelin contracts,
the docs need to be regenerated. Each time that the
contracts are built, these files are generated.
Merging this commit will make dev on alternative things
less noisy.

* op-bindings: regenerate

The build was missed someplace and is now breaking ci everywhere

* ci: build monorepo with op-bindings change

Address this warning: Unknown section [default] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run .

parameterize project

Switch to artifact registry
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Version Packages

Develop -> Master 

ops: new ci-builder

Includes new version of foundry

Bumps [@openzeppelin/contracts-upgradeable](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable) from 4.4.0 to 4.7.1.
- [Release notes](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/releases)
- [Changelog](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/blob/master/CHANGELOG.md)
- [Commits](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/compare/v4.4.0...v4.7.1)

---
updated-dependencies:
- dependency-name: "@openzeppelin/contracts-upgradeable"
  dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

contracts-bedrock: print receipt after deposit

contracts-bedrock: fix imports

* feat(sdk): Update the Goerli SCC contract address to the new value

* feat(sdk): Bump the SDK version to 1.3.1
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Updates the SDK to throw a better error when the user provides a bad
chain ID. Would've helped an end-user more easily debug an issue where
the chain ID parameter was missing.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Updates the TypeScript build to also generate ABI objects that can be
imported on the client-side. Specifically necessary so that these ABIs
can be imported on the frontend where fs/glob is not available.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Introduces a new SentMessageExtraData event to the CrossDomainMessenger
base contract. We need this event so that we can properly find all
relevant message data in the SDK. SDK cannot function without this
event. We also cannot add to the old SentMessage event without breaking
the ABI of our contract, so we're stuck adding an extra data event.