test(extensions): migrate to createRuleTestCaseFunction

[marcalexiei]

Follow up of #176.

extensions rule right now has two messages:

eslint-plugin-import-x/src/rules/extensions.ts

Lines 169 to 173 in 75c4e36

	messages: {
	missing: 'Missing file extension {{extension}}for "{{importPath}}"',
	unexpected:
	'Unexpected use of file extension "{{extension}}" for "{{importPath}}"',
	},

missing message is populate here:

eslint-plugin-import-x/src/rules/extensions.ts

Lines 262 to 266 in 75c4e36

	messageId: 'missing',
	data: {
	extension: extension ? `"${extension}" ` : '',
	importPath: importPathWithQueryString,
	},

However testing this message with extensiondata property set like extension: '"js" ':

test({
  code: '...'
  errors: [
    { messageId: 'missing', data: { extension: '"js" ', importPath: './foo'  } }
  ]
})

Seems a bit awkward IMHO.

---

To simplify extension data property I added a separate message missingKnown.

I also refined Options type.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7dc3480

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a 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.

[SukkaW]

LGTM, thanks!