chore(analytics): updates staging proxy url for amplitude

[ygrishajev]

Summary by CodeRabbit

• Chores
  • Reorganized environment configuration by moving settings from base configuration to environment-specific files for production and staging deployments.

[coderabbitai]

📝 Walkthrough

Walkthrough

Environment configuration for the Amplitude proxy URL is being migrated from the shared .env file to environment-specific files, with production and staging instances using different endpoints (console-proxy and console-proxy-beta subdomains respectively).

Changes

Cohort / File(s)	Summary
Amplitude Proxy Configuration apps/deploy-web/env/.env, apps/deploy-web/env/.env.production, apps/deploy-web/env/.env.staging	Removed NEXT_PUBLIC_AMPLITUDE_PROXY_URL from base .env and added environment-specific values to .env.production (console-proxy.akash.network) and .env.staging (console-proxy-beta.akash.network).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat(analytics): proxies amplitude requests to avoid failed requests due to blockers #2441: Implements code and schema to consume the NEXT_PUBLIC_AMPLITUDE_PROXY_URL variable that is being repositioned in this PR.
• fix: moves amplitude on a separate subdomain #2652: Also modifies the NEXT_PUBLIC_AMPLITUDE_PROXY_URL configuration for deploy-web across environment files.

Suggested reviewers

• stalniy
• baktun14

Poem

🐰 The proxy hops from .env to staging's door,
With production paths that route evermore,
Each subdomain tweaked with hop and bound,
Analytics proxies safely configured round! 🎯

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: updating the staging proxy URL for Amplitude analytics. However, the changes also include removing the variable from .env and adding it to .env.production, which are not mentioned in the title.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/analytics

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.60%. Comparing base (823030c) to head (7cae3f3).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2655      +/-   ##
==========================================
- Coverage   51.41%   50.60%   -0.81%     
==========================================
  Files        1050     1018      -32     
  Lines       29531    28750     -781     
  Branches     6634     6538      -96     
==========================================
- Hits        15184    14550     -634     
+ Misses      14064    13919     -145     
+ Partials      283      281       -2     

Flag	Coverage Δ		*Carryforward flag
api	78.31% <ø> (-0.33%)	⬇️	Carriedforward from f945c14
deploy-web	32.75% <ø> (ø)
log-collector	?
notifications	87.94% <ø> (ø)		Carriedforward from f945c14
provider-console	81.48% <ø> (ø)		Carriedforward from f945c14
provider-proxy	84.35% <ø> (ø)		Carriedforward from f945c14
tx-signer	?

*This pull request uses carry forward flags. Click here to find out more.
see 46 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.