fix: set the context when overwriting .clock command

[Hugo-Hache]

User facing changelog

Previously overwriting .clock command crashed because it did not preserve this context. Now the following works:

Cypress.Commands.overwrite('clock', (originalCommand, ...args) => {
  return originalCommand(...args)
})

cy.clock()

Additional details

This MR is vastly inspired from #9589

PR Tasks

• Have tests been added/updated?
• Has the original issue or this PR been tagged with a release in ZenHub?
• [na] Has a PR for user-facing changes been opened in cypress-documentation? Link
• [na] Have API changes been updated in the type definitions?
• [na] 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.

[CLAassistant]

All committers have signed the CLA.

[Hugo-Hache]

Thanks @bahmutov for #9589, without it I would never have been able to know how to fix the crash I was facing.

[jennifer-shehane]

@Hugo-Hache Thanks for signing the CLA, unfortunately one of the authors of the commits does not match the email address on your GitHub account. Our CLA bot gets confused when they don't match. Here are some solutions to fixing when commits are linked to the wrong user: https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

[jennifer-shehane]

Update CLA signature

[Hugo-Hache]

@jennifer-shehane I just fixed the identity of my first commit to match my GitHub account. Thanks for the notice.

Dismissing my review

[cypress-bot]

Released in 9.1.1.

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