chore(analytics): Allow analytics to be configured per env

[ilmotta]

Fixes #21974

Summary

Allows MixPanel to be configured per environment. The hardcoded MixPanel app ID and token are removed from the code (see the parent issue for more details). The token can be exploited and that's by design in analytics tools https://developer.mixpanel.com/reference/project-token, but we are being too kind at the same time, so I'm removing that from code ;)

Areas that may be impacted

• Analytics

Steps to test

I will test this PR myself.

• Enable usage data during onboarding and from settings.
• Check the events are published to the correct MixPanel project.

Note: to test the correct values are set-up in Jenkins for release builds we need to generate a release build. That's the reason I committed a change to the VERSION file with the PR number, as I believe this is the recommendation from infra team.

status: ready

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	61bf682	#3	2025-01-22 15:34:15	~5 min	tests	📄log
✔️	61bf682	#3	2025-01-22 15:38:11	~9 min	android-e2e	🤖apk 📲
✔️	61bf682	#3	2025-01-22 15:39:06	~10 min	android	🤖apk 📲
✔️	61bf682	#3	2025-01-22 15:41:07	~12 min	ios	📱ipa 📲

[ilmotta]

Thanks for the swift reviews guys!

---

@siddarthkay I tagged you as a reviewer to help us configure the vars in Jenkins. The shadow-cljs code already allows passing the vars to the initialization code in status-go, so I believe it's just a matter of passing down the vars from Jenkins. The parent issue has the details about what we expect to be configured #21974 in Jenkins. When the time is appropriate for you, could you help us by adding the vars to Jenkins? Thanks!