[IATR](M1.0) "Run Failures" button enhancements

[warrensplayer]

Updates to the behavior of the "Run Failures" button in the DebugSpec component

• Add a tooltip when the button is disabled that says "Spec was not found locally"

* Update disabled/enabled based on local polling * the existing logic that is being used to monitor changes in spec files will be used to drive the setting of the `isDisabled` prop for the component. Confirm with a test that changing the prop on an already mounted component will update the button/link

• Show CTA in tooltip for switching testing types if needed
  • The isDisabled flag will also be false for a spec if the testing type for the spec does not match the current testing type for the Cypress app. Add a new flag to the component to let it know it needs to switch to a new testing type in order to run this test locally. Then show a different tooltip shown in the designs below.
  • If the App is in E2E mode and the test is a component test, and the local project is configured for component testing
    • Text: "There are {failedSpecCount} component tests failing in this spec. To run them locally, switch to component testing"
    • CTA: "Switch to component testing" - clicking the button should reload the app in the component testing mode
  • If the opposite situation:
    • Text: "There are {failedSpecCount} E2E tests failing in this spec. To run them locally, switch to E2E"
    • CTA: "Switch to E2E testing" - clicking the button should reload the app in the E2E testing mode

Clickup: https://app.clickup.com/t/18033298/PM-2546
Figma Flow

[warrensplayer]

Hey team! Please add your planning poker estimate with Zenhub @amehta265 @astone123 @lmiller1990 @marktnoonan @mike-plummer @rockindahizzy @ZachJW34

[cypress-bot]

The code for this is done in cypress-io/cypress#25234, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[lmiller1990]

Closing since resolved in #25234

[emilyrohrbough]

Released in 12.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.5.0, please open a new issue.