* fix: correct FailedDatabase counter for upsert_disbursement

Previously we would always increment the counter instead of adding the
number of failed upserts observed.

* feat: expose teleportr-api metrics server
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* refactor: Remove unused network name param from contract deploy configs

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

* valid openapi

* integer format

* 64 bit integer in requests
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Version Packages

Develop -> Master

proxyd: Add changeset for release

Develop -> Master

* feat: add go packages to package.json

* feat: correct conf_remaining calculation

Subtaction was being performed in the wrong order, causing underflow.

- Adopts Go workspaces for future compatibility with the Bedrock move into the monorepo
- Moves Go packages to the root of the repo in order to fix import paths
- Rewrites existing Go import paths
- Removes Stackman, since it's not needed anymore
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* refactor: replace calls to getNetwork() with getChainId util

* requested changes

Cleans up tests for all Library contracts using same techniques as
previous PRs.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Removes the Helper_SimpleProxy contract by replacing code that relies on
it.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* go/proxyd: Proxy requests as batched RPC

We forward several RPC request objects to upstreams using the JSON-RPC
batch functionality. This should be more efficient than serialized RPC
request proxying the round-trip latency of the remaining request objects
are eliminated.

A new server config, `max_upstream_batch_size`, is introduced to limit
the number of RPC request objects in a single batch request. This is to
avoid overloading upstream as proxyd may accept a large number of
request objects in a single request by having a large `max_body_size_bytes`
config value.

* remove flakes: no more SequencedResponseHandler
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Develop -> Master

Version Packages

Develop -> Master

The nightly testnet environment must override the Optimism contracts addresses on L1.
Otherwise, it defaults to the prod contracts deployed on goerli which
isn't compatible with the nightly setup.

Develop -> Master

Version Packages

Develop -> Master

Several tests were failing with out of gas errors because they began executing before their
wallets were adequately funded.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

Cleans up the TeleportrDisburser tests using the same techniques as in
previous cleanup PRs.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

Adds a one-liner for getting chain ID given an ethers.Provider input.
Going to follow this PR up with a good first issue to use this util
wherever we're trying to get the chain ID.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

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

Another test cleanup, this time for AddressDictator, ChugSplashDictator
and WETH9. Putting them in the same PR since 2 of the files have very
few changes.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

tasks: compute calldata cost diff in `fetch-batches`

Since this issue: https://github.com/ethereum-optimism/optimism/issues/2280
was openned, there were other entries added to "nohoist", so I just
removed the "examples/*" entry.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Develop -> Master

Version Packages

Develop -> Master

Logging the entire RPC request can be too "expensive" when logging request
objects in a large JSON-RPC batch request. We log the raw HTTP request
body instead so we can truncate effectively when the entire body
exceeds the maxLogLength.