test: enable profiling skip onboarding for performance

[cortisiko]

Description

The purpose of this PR is the evolution of our performance tests. Currently, our performance test runs on a nightly cadence during off-peak (11 pm EST). The idea is to speed up the tests so that it does not take 50+ minutes to run. In order to do so, we create and use 2 different types of e2e builds to cover the different types of performance tests that we have:

• Performance tests that go through onboarding - These need a fresh app without any pre-imported wallet data.
• Performance tests that don't rely on onboarding - These need an app with a pre-imported wallet (using SRP and password) to skip the onboarding flow This is based on the work Tomas did here.

The Approach

The build pipeline follows a hybrid model: Android builds run directly on GitHub Actions with our custom runners, while iOS builds are generated through Bitrise via API calls.

TLDR;

• Performance E2E workflow triggers both build workflows
• Android builds run directly on GitHub Actions runners, creating two APK files
• iOS builds are triggered on Bitrise, then we download the IPA files via API
• Both APK and IPA files get uploaded to BrowserStack, and URLs are returned
• Performance tests run using the appropriate build type for each test scenario

APIs Used

Bitrise API for iOS builds:
/apps/{app-slug}/builds - Retrieves list of builds
/apps/{app-slug}/artifacts/{artifact-slug} - Downloads IPA artifacts

BrowserStack API for app uploads:
https://api-cloud.browserstack.com/app-automate/upload

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.

[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

[javiergarciavera]

LGTM!