ci: add Playwright Appium test health report workflow

[cmd-ob]

Description

Adds a scheduled GitHub Actions workflow that aggregates Playwright JSON artifacts from Appium smoke runs on main (ci.yml) and posts infra/flaky/watch test summaries to Slack via the playwright-test-health-report action (github-tools, merged in #262).

Pinned to MetaMask/github-tools@4a2ddd75. Runs weekdays at 10:00 and 15:00 UTC, with workflow_dispatch and a configurable lookback window. Uses SLACK_WEBHOOK_PLAYWRIGHT_HEALTH_REPORT.

Changelog

CHANGELOG entry: null

Related issues

Refs: Appium CI health reporting follow-up to #31730 / #31756

Manual testing steps

Feature: Playwright Appium test health report

  Scenario: PR trigger posts report to Slack
    Given SLACK_WEBHOOK_PLAYWRIGHT_HEALTH_REPORT_TEST was configured in repo secrets
    And this PR was open against main with a temporary pull_request trigger
    When the pull_request workflow ran on playwright-test-health-report.yml changes
    Then a Playwright Test Health Report (Mobile Appium) message appeared in Slack (see screenshot)

  Scenario: Scheduled report after merge to main
    Given the workflow exists on main with SLACK_WEBHOOK_PLAYWRIGHT_HEALTH_REPORT configured
    When the weekday schedule runs or an engineer triggers workflow_dispatch with lookback_days=1
    Then the report is generated from main ci.yml Playwright JSON artifacts

Screenshots/Recordings

Before

N/A — new workflow only.

After

Slack report from PR test run (1-day lookback on main Appium smoke):

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

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.

Made with Cursor

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