chore(card): cp-7.58 add new Baanx API key environment variables on build.sh

[Brunonascdev]

Description

Add new MetaMask Card Baanx variable mappings to the build.sh script

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• 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.

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.

---

Note

Adds MM_CARD_BAANX_API_CLIENT_KEY env remaps across build environments and updates Baanx URL mapping so rc uses PRD.

• Build/CI:
  • Map MM_CARD_BAANX_API_CLIENT_KEY_* to MM_CARD_BAANX_API_CLIENT_KEY across environments in scripts/build.sh:
    • DEV→MM_CARD_BAANX_API_CLIENT_KEY (dev)
    • UAT→MM_CARD_BAANX_API_CLIENT_KEY (qa, e2e, test, flask test/e2e, experimental)
    • PROD→MM_CARD_BAANX_API_CLIENT_KEY (production, beta, rc, flask prod)
• Config:
  • Rename example var in .js.env.example to MM_CARD_BAANX_API_CLIENT_KEY_DEV.
• Card util:
  • In mapBaanxApiUrl.ts, map rc environment to AppConstants.BAANX_API_URL.PRD (was DEV).
• Tests:
  • Update expectations in mapBaanxApiUrl.test.ts for rc to use PRD and adjust comprehensive mapping table.

^{Written by Cursor Bugbot for commit 50d4b9d. This will update automatically on new commits. Configure here.}

[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
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud