[IATR] E2E Tests for IATR

[baus]

When working through the IATR M0 and M1 stories, the focus was on writing component tests for the new front end features and updating existing end-to-end tests. To complete the milestone, the CT tests need to be supported with E2E tests focused on the new functionality.

These tests should be branched off the stokes/IATR-M0-cloud-run-data branch for the #25316 PR unless it is been merged to the feature branch feature/IATR-M0

The following areas need to be covered:

• Sidebar
  • See feat: debug status badge #25152
• Debug page
  • Empty states
    • These are similar if not the same as the Runs page. So scenarios can be copied from there
    • See feat: IATR empty states #25219
  • Non failure run statuses
    • See feat: IATR non-failure run statuses #25286
    • See feat: Add messaging for retention state exceeded #25361
  • Failed build showing failed specs
    • Failed build with only one group
    • Failed build with multiple groups
    • See feat: IATR-M1.0 Debug Spec component update #25263
  • Banners shown for "next" run
    • Completed state with running next state
    • Completed state with running next state that completes while on the page
    • See feat: IATR relevant run status banner #25282
  • Navigating to external link for Cypress Cloud
  • Using the "Run failures button"
    • Opening test runner to run failed tests
    • Opening tooltip to change test type
    • See feat: run failures enhancements #25234

[lmiller1990]

I have moved this back to the Sprint Backlog from In Progress.