feat: Debug failed test limit (#25418)

[mike-plummer]

• Closes IATR M1.0 - Add banner when failed test count > 100 #25418

User facing changelog

No changelog entry, part of IATR feature

Additional details

• Restricting gql query to pull back max of 100 failed tests to guard against very large suites with lots of failing tests
• Adding new info banner to inform user to 100 test limit being exceeded

Steps to test

Component tests have been updated, easiest way to test is to work with mock data in those

How has the user experience changed?

New Banner

New Banner (narrow viewport)

New Banner (no cloud run url available)

New banner being displayed in DebugContainer (note mocked data so test count does not actually match here)

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

---

Test summary

5220 • 0 • 108 • 0 • 2

---

Run details

Project	cypress
Status	Passed
Commit	bf5fb2c
Started	Jan 12, 2023 2:04 PM
Ended	Jan 12, 2023 2:16 PM
Duration	12:07 💡
OS	Linux Debian -
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	commands/net_stubbing.cy.ts		1
1	network stubbing > intercepting request > can delay and throttle a StaticResponse
	e2e/origin/commands/waiting.cy.ts		1
1	cy.origin waiting > alias > waits for the route alias to have a response

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[rockindahizzy]

Worked as expected!

[warrensplayer]

Looks great!