fix(spy)!: reset existing spy on repeated spyOn

[hi-ogawa]

Description

• Closes Feature Request: Create spyReset to only reset spies, not other mocks #7348

Is this a breaking change again? 🤔

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[sheremet-va]

Why do we need to restore it? I would expect we can just reset the state

[hi-ogawa]

mockReset would be weird. I pushed it to show how tests fail. The previous issue #6419 will come back at least.

[hi-ogawa]

Or probably 346794b is what you meant?