test: Update env variables for appium upgrading on bitrise.yml

[SamuelSalas]

Description

Currently, the env variables values required to run the Appium Upgrading test cases on bitrise.yml are deprecated. Browserstack constantly eliminates a build after 30 days of it being generated. The variables affected are:

PRODUCTION_APP_URL: 'bs://c2c414d2b4935096274bd2fb98232cc7b8408b2a'
PRODUCTION_BUILD_NAME: 7.24.4
PRODUCTION_BUILD_NUMBER: 1354
So its required to update the values from a valid QA build saved on Browserstack.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4a5b0c5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2fbbd881-fcd9-4948-94fb-f8ada416cc3c

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

[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 SonarCloud