User Story:
As a developer, I want to create a utility script that pulls and exports all relevant ENV variables for any environment to local ENVs and update Pulumi scripts to read these variables, so that I can run pulumi up from my local environment for review, staging, and production using the correct variables.

!! Note from Lucian !! : I'll update the pulumi scripts as part of #2627, so this ticket can just handle the script for local development. Or really, setting up a .env.local with the right 1password paths and then altering the package.json commands to use the 1password utility, and making sure 1password has good default entries for local dev. See https://developer.1password.com/docs/cli/secrets-environment-variables/

Acceptance Criteria:
GIVEN the utility script and updated Pulumi scripts,
WHEN I run the script,
THEN all relevant environment variables should be pulled and exported to my local environment, and the Pulumi scripts should use these variables.

Tech Details:

• see https://developer.1password.com/docs/cli/secrets-environment-variables/ for more details
• Develop a script to pull and export environment variables.
• Ensure the script works for review, staging, and production environments.
• Modify the Pulumi script to use external environment variables, including NEXT_PUBLIC_MAX_LEGACY_ROUND_ID.
• Document usage instructions.

Open Questions:

• Should the script handle any environment-specific logic?

• Are there additional environment variables that need to be considered?

Notes/Assumptions:

• Assume developers have local environments set up correctly.
• Assume all required environment variables are available.