Removes getMessagesByAddress from the SDK until we can get the function
to work properly. Likely requires the indexer to be integrated into the
SDK or to figure out some new way to quickly get all of the data we
need. Better to comment this out to avoid confusion.

Infra repo, add op-replica

minor teleportr API fixes

This commit fixes:
 * A bug in /status where is_available always returns false.
 * A bug in /track where the "teleport" key was incorrectly capitalized.
 * A bug in /track and /history where disbursements were never
   populated, also changes the behavior to show null when the
   disubrsement has not been processed.

ci: publish indexer docker image

various small BaseServiceV2 improvements

docs: update contributing.md for exit code 137

Error message when this happens can be unhelpful sometimes

feat: add teleportr API server

Set the message-relayer package to private

Improves the log lines within BaseServiceV2 when the service is being
shut down. Follows the pattern already laid out in the main() function
which will log when key events happen.

Fixes the snake case function for metric names to properly account for
strings which include "L1" or "L2". Normally these would be split into
"L_1" and "L_2" respectively, but we want to join these since they're
quite common and "L_1" looks silly.

These will be used to facilitate HTTP requests to the API server.

This will ensure performance on queries for a specific deposit by
txn_hash/address does not degrade as the table grows.

maint: clear dependency warnings

chore: change service generated env variables

Clears out most of the dependency warnings (mainly unmet peer dependency
warnings) by adding or updating various dependencies. Still seeing two
warnings that can only be fixed by updating to the latest hardhat. See
discussion in #2260 for more context about our attempts to upgrade to
the latest version of hardhat.

Version Packages

Develop -> Master

indexer: add pagination metadata for deposit, withdrawal endpoints

proxyd: Don't hit Redis when the out of service interval is zero

ops: Fix gas oracle in docker compose

When the out of service interval is zero, `proxyd` will send a `SETEX` command to Redis with a zero expiry. This is technically an error, and causes messages like `error setting backend unavailable ERR invalid expire time in setex` to appear in the logs. Users won't notice the issue since `proxyd` can continue working when Redis returns an error, but we should clean this up nonetheless since these problems appear in our alerting.

Delete unused variables

feat: extract gas limit estimation to driver, add 20% buffer

feat: add MIN_L1_TX_SIZE configuration

feat(cmn): gracefully handle BaseServiceV2 exits