test(eslint-plugin): migrate from Jest to Vitest

[timdeschryver]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngrx/platform/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] Other... Please describe:

What is the current behavior?

Unit tests for eslint-plugin are run with Jest.

Closes #

What is the new behavior?

Unit tests for eslint-plugin are run with Vitest.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[netlify]

✅ Deploy Preview for ngrx-io canceled.

Name	Link
🔨 Latest commit	6d02ee6
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/67fea5383a395d0008603f16

[brandonroberts]

🤝

[rainerhahnekamp]

Cool stuff.

Not part of this PR, but the question for me is, if we want to keep the global definitions or if we also want to do explicit imports with describe, it, expect, etc. Explicit imports would improve support in IDEs (although it might not be necessary, when vite.config.ts is present).

[brandonroberts]

The explicit imports can be used when testing without zone.js, but the global definitions are required when zone.js is used due to the patching of the describe, it, expect, etc functions.

[rainerhahnekamp]

@brandonroberts, ah good to know. Thanks for the info Brandon