test: migrate to createRuleTestCaseFunction

[marcalexiei]

I migrated the first 10 rules test files.

Aside from a fix on first rule where value was missing in Options type everything should work like a charm.
(I added a changeset but unless someone is extracting the type from the rule export nothing will change on user land)

Do you prefer that I continue to push on this PR or do you prefer that I open subsequent PRs to divide the review effort?

[changeset-bot]

🦋 Changeset detected

Latest commit: b130ac4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
eslint-plugin-import-x	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[marcalexiei]

Yesterday the task was working

Today is not

It seems an issue with eslint: eslint/eslint#19134.
Relative eslint-plugin-unicorn issue: sindresorhus/eslint-plugin-unicorn#2496

I assume that the following steps in CI workflows ends up installing the last version of eslint:

eslint-plugin-import-x/.github/workflows/ci.yml

Lines 56 to 63 in 14fc608

	- name: Install ESLint ${{ matrix.eslint }}
	run: |
	yarn add -D --ignore-engines eslint@${{ matrix.eslint }}
	- name: Install Dependencies
	run: yarn --ignore-engines
	env:
	SKIP_YARN_COREPACK_CHECK: 1

eslint-plugin-import-x/.github/workflows/ci.yml

Lines 24 to 27 in 14fc608

	eslint:
	- '8.56'
	- '8'
	- '9'

Replacing 9 with 9.14 makes CI green again.

---

I just want to report that on the failing CI the eslint version printed in the error is 9.8.0 which seems wrong since the error is present on 9.15.0.

[SukkaW]

It seems that the issue comes from the typescript-eslint now. Let's wait and see if bumping typescript-eslint would be possible.

[SukkaW]

Do you prefer that I continue to push on this PR or do you prefer that I open subsequent PRs to divide the review effort?

You can either continue to push to this PR or subsequent PRs, I am OK with both.

If you are going to continue to push to this PR, it would be better to convert this PR to a draft.