feat: add env vars mapping in build script

[NicolasMassart]

Description

• add env vars mapping in build script
• add calls to qa and release steps
• update flask function

For QA, envs are suffixed by the Segment source suffix: for QA by QA, for release by PROD and for flask by FLASK.
example: SEGMENT_WRITE_KEY_QA remaps to the app SEGMENT_WRITE_KEY

Related issues

Fixes #8769

Manual testing steps

1. Go to bitrise QA build
2. Run the built dapp and check that events are landing on the correct source (use Segment source debugger)

Screenshots/Recordings

NA

Before

NA

After

NA

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 53cc46e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a6e1948a-b1b6-4013-94b5-a1e756960c54

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sethkfman]

LGTM

[Cal-L]

LGTM

[metamaskbot]

Missing release label release-7.18.0 on PR. Adding release label release-7.18.0 on PR and removing other release labels(release-7.19.0), as PR was cherry-picked in branch 7.18.0.