feat!: rename mock types to match jest's

[sheremet-va]

Current types were names without much consideration about compatibility with Jest, or any actual thought behind it 👀

I think we might as well align them with Jest. This is a breaking change

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9feccf0
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/62b4090a74b53400086ce9bd
😎 Deploy Preview	https://deploy-preview-1525--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[antfu]

Maybe we could do type alias like:

export type MockContext = SpyContext

[sheremet-va]

Maybe we could do type alias like:

export type MockContext = SpyContext

What would be the benefit? Avoid breakage? Again, the current names were chosen on a whim 😄 We can support both, but I don't see a reason, tbh 👀

[antfu]

We have SpyInstanceFn renamed to Mock, but kept SpyInstance, which feels a bit inconsistent to me. Should we also rename it, or we just have two set of naming logic.

[sheremet-va]

We have SpyInstanceFn renamed to Mock, but kept SpyInstance, which feels a bit inconsistent to me. Should we also rename it, or we just have two set of naming logic.

jest has SpyInstance 😄 I've added an alias for MockInstance, since jest also has that one.