test: upload Test Plan JSON file to artifacts

[sleepytanya]

Description

Fix broken Test Plan JSON link by uploading as GitHub Actions artifact instead of gh-pages (which is blocked by branch protection).

Changes

• Replace gh-pages upload with actions/upload-artifact@v4 (unzipped)
• Update PR comment to link to build workflow for artifact access

Changelog

CHANGELOG entry: null

Related issues

Fixes:
https://consensyssoftware.atlassian.net/browse/MCRM-69

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
The two changed files are purely CI/CD infrastructure changes with no impact on app code or E2E test flows:

1. .github/workflows/build-rc-auto.yml: Replaces a complex git-based upload to a gh-pages branch with a simpler actions/upload-artifact@v4 action. This is a workflow simplification — the test plan JSON is now stored as a GitHub Actions artifact instead of being committed to a gh-pages branch. No app code, test logic, or user flows are affected.

2. scripts/build-announce/test-plan-section.ts: Updates the markdown text in the build announcement to reference the new artifact location instead of a GitHub Pages URL. This is a string/URL change in a build script, not in any app code.

Neither change touches:

• Any app source code or components
• Any E2E test files or test infrastructure
• Any controllers, Engine, or core modules
• Any UI components or user flows
• Any performance-sensitive code paths

These are low-risk CI/CD housekeeping changes. No E2E tests are needed to validate them — the changes only affect how the RC build workflow stores and references the test plan artifact.

Performance Test Selection:
The changes are purely CI/CD infrastructure changes affecting how the test plan JSON artifact is stored and referenced. No app code, rendering, data loading, or performance-sensitive paths are touched. Performance tests are not warranted.

View GitHub Actions results

[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

[Cal-L]

LGTM