[ECO-2436] Add Aptos API keys to the Aptos client anywhere we use it

[xbtmatt]

Description

Add the Aptos API keys to the environment variables and use it in the Aptos client class everywhere, including the sdk and the frontend and the docker container for e2e tests.

Resolve the key by the network, so we don't have to update environment variables for each build but rather provide them all at once, like so:

NEXT_PUBLIC_LOCAL_APTOS_API_KEY="" # Blank is fine for local, since it ignores it.
NEXT_PUBLIC_CUSTOM_APTOS_API_KEY="" # We only use `custom` for local as of right now, so same as above.
NEXT_PUBLIC_DEVNET_APTOS_API_KEY="AG-key1"
NEXT_PUBLIC_TESTNET_APTOS_API_KEY="AG-key2"
NEXT_PUBLIC_MAINNET_APTOS_API_KEY="AG-key3"

Testing

We use it everywhere now so it should fail in any SDK or frontend tests that use the Aptos client class.

Checklist

• Did you update relevant documentation?
• Did you add tests to cover new code or a fixed issue?
• Did you update the changelog?
• Did you check all checkboxes from the linked Linear task?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
emojicoin-dot-fun	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 19, 2024 2:13am
emojicoin-dot-fun-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 19, 2024 2:13am