fix(navigation): resolve wait on canceled requests

[adamalston]

• Closes Cancelled network requests fail to resolve with cy.wait #19326

Additional details

I left a TODO with some questions that hopefully someone can answer.

Steps to test

Revert the fix and check that the test fails.

How has the user experience changed?

N/A

PR Tasks

• Have tests been added/updated?
• [~] Has a PR for user-facing changes been opened in cypress-documentation?
• [~] Have API changes been updated in the type definitions?

---

Note

Marks in-flight requests as errored at navigation start so cy.wait('@alias') resolves when the underlying request is canceled by navigation; adds test and changelog entry.

• Driver (navigation):
  • Mark in-flight network requests and aliasedRequests as canceled on navigation start by setting request.state = 'Errored' and attaching an error in stabilityChanged() within packages/driver/src/cy/commands/navigation.ts.
• Tests:
  • Add e2e test in packages/driver/cypress/e2e/commands/navigation.cy.js verifying cy.wait('@alias') resolves after a navigation-canceled request.
• Changelog:
  • Add bugfix note to cli/CHANGELOG.md for cy.wait('@alias') timing out on navigation-canceled requests.
• Misc:
  • Add ESLint suppression for console in packages/electron/src/print-node-version.ts.

^{Written by Cursor Bugbot for commit f670c41. This will update automatically on new commits. Configure here.}

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[adamalston]

Regarding the changes in a623e1f:

• The pre-commit hook would not pass without the update in packages/electron/lib/print-node-version.ts.
• I did not make the change in npm/cypress-schematic/src/schematics/utils/index.ts. It appears to have been made automatically.
• I did not move the changelog entry. I don't seen any benefit in moving it and creating additional conflicts before the code is reviewed.

[AtofStryker]

My opinion @adamalston would be to do nothing since an error in the Cypress log would likely confuse the user. @jennifer-shehane anything you want to add here?