[Phase 6] Report E2E results to GitHub

[kieran-osgood-shopify]

Stack Context

This is Phase 6 of the BrowserStack Maestro E2E stack for Checkout Kit, stacked on BrowserStack Maestro execution.

Parent issue: https://github.com/shop/issues-checkout-kit/issues/1100
Epic: https://github.com/shop/issues-checkout-kit/issues/1084

Why?

Developers should not need to search BrowserStack manually to understand a failed E2E run. Failures should link directly to the actionable artifacts, while green runs should avoid comment noise.

What?

Adds GitHub reporting for E2E results:

• sticky PR failure comment with a marker
• failure-only PR comment behavior
• actionable failure markdown with device selector, resolved device, suite path, BrowserStack build URL, video, screenshots, Maestro commands/logs, device logs, and network logs
• Bitrise report workflow wiring

Results

When one suite is failing

After fixing all the tests you'll see the workflow update the comment

[kieran-osgood-shopify]

• [Phase 7] Soft-launch E2E PR checks #364 : 2 dependent PRs (#401 , #417 )
• [Phase 6] Report E2E results to GitHub #363 👈 (View in Graphite)
• [Phase 5] Run BrowserStack Maestro from E2E matrix rows #362
• [Phase 4] Build React Native iOS E2E IPA artifact #361
• [Phase 3] Build React Native Android E2E APK artifact #360
• [Phase 2] Add Bitrise E2E pipeline skeleton #357
• [Phase1] Add E2E matrix launch smoke foundation #356
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.