fix: Use CYPRESS_VERIFY_TIMEOUT as integer

[tbiethman]

• Closes CYPRESS_VERIFY_TIMEOUT TypeError: Expected the timeout option to be a non-negative integer, got 100000 (string) #19476

User facing changelog

• CYPRESS_VERIFY_TIMEOUT is now used as an integer rather than a string

Additional details

This change allows the CYPRESS_VERIFY_TIMEOUT environment variable to work appropriately when set by the user. The test cases were also updated to be more strict in their assertions.

How has the user experience changed?

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)
• [n/a] Has a PR for user-facing changes been opened in cypress-documentation?
• [n/a] Have API changes been updated in the type definitions?
• [n/a] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• 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.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

18917 • 0 • 218 • 0 • 1

---

Run details

Project	cypress
Status	Passed
Commit	faf502f
Started	Jan 3, 2022 2:52 PM
Ended	Jan 3, 2022 3:04 PM
Duration	11:59 💡
OS	Linux Debian - 10.10
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/commands/net_stubbing_spec.ts		1
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"

---

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