Consolidate env prod vs dev keys usage

[jinchung]

Related to APP-2008

What changed (plus any additional context for devs)

• Cleans up more unused configs
• Consolidates some keys that are prod vs staging (will create a separate followup PR for creating separate staging vs prod configs.)
• Associated with: https://github.com/rainbow-me/rainbow-env/pull/73

Screen recordings / screenshots

What to test

• wallet data still behaves as expected
• NFT related data (mints, offers, nft metadata) looks the same

[linear]

APP-2008 Consolidate prod vs dev keys

[walmat]

LGTM. One question: Why do we alias some env vars inside env.ts and not some others? One example in this PR is RESERVOIR_API_KEY

[brunobar79]

Launch in simulator or device for 74e7f59

[jinchung]

LGTM. One question: Why do we alias some env vars inside env.ts and not some others? One example in this PR is RESERVOIR_API_KEY

I think it started off with the IS_PROD vs not and some were added there in order to distinguish between PROD vs STAGING envs and expose them. Now that we don't need to do that for the RESERVOIR key, I'll follow up in another cleanup PR and remove the instances that use the env.ts for it.

[brunobar79]

Launch in simulator or device for 3da66cc