feat: add type-checking with jsdoc TypeScript types and publish types

[bmish]

Fixes #241.

This PR enables the checkJs TypeScript option for this plugin's codebase which requires us to add jsdoc type annotations anywhere types are missing. It also exports types for anyone who uses TypeScript in their eslint.config.js/ts.

The majority of the changes in this PR involve adding type annotations as well as adding type guards (checking node types).

Challenges:

• Some types were tricky to get right
• Some types required required refactoring to get right
• Some node types needed to use import('eslint').Rule.Node when the node parent was provided by ESLint but others needed import('estree').Node when ESLint did not add the parent

It's likely this fixes a bunch of unknown bugs from not correctly checking node types or not checking for null/undefined variables.

This should significantly improve the developer experience from having autocomplete and type information available.

Follow-up PRs to consider:

• This sets us up nicely for a future ESM/TypeScript conversion.

This took 10+ hours to do by hand. Cursor was helpful for autocomplete.

Related examples:

• [New] add TypeScript types import-js/eslint-plugin-import#3097
• Add TypeScript declaration file sindresorhus/eslint-plugin-unicorn#2382
• feat: add types to package jest-community/eslint-plugin-jest#1667
• Include types in published eslint-plugin-next vercel/next.js#78109

Follow-up fixes I needed to get this to work:

• fix: entrypoint #583
• fix: package.json path #584
• chore: eslint ignore dist/ #585
• fix: ensure release-it runs the build #586
• fix: crash when loading loading package.json in index.js #587
• fix: false positive in literal-compare-order rule #601
• chore: ignore dist/ for nyc test coverage #602

[bmish]

There's a number of old rules I had to remove because they conflict with prettier.

[bmish]

This rule is deprecated and didn't appear to be compatible with the jsdoc TypeScript comments I added. We can replace with https://github.com/gajus/eslint-plugin-jsdoc later.

[bmish]

Unfortunately, I had to reduce test coverage requirements because of the 100+ type guards I added. Some type guards could be tested, while most would necessitate /* istanbul ignore */ comments. We can add tests or ignore comments later as it would be very time-consuming to do so.

[coveralls]

Pull Request Test Coverage Report for Build 15933563230

Details

• 169 of 242 (69.83%) changed or added relevant lines in 26 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-7.9%) to 92.058%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
eslint-remote-tester.config.mjs	0	1	0.0%
lib/rules/literal-compare-order.js	7	8	87.5%
lib/rules/no-assert-logical-expression.js	6	7	85.71%
lib/rules/no-commented-tests.js	2	3	66.67%
lib/rules/no-conditional-assertions.js	1	2	50.0%
lib/rules/no-early-return.js	1	2	50.0%
lib/rules/no-setup-teardown.js	4	5	80.0%
lib/rules/no-throws-string.js	1	2	50.0%
lib/rules/assert-args.js	7	9	77.78%
lib/rules/no-compare-relation-boolean.js	2	4	50.0%

Files with Coverage Reduction	New Missed Lines	%
lib/utils.js	1	92.92%

Totals
Change from base Build 15890712979:	-7.9%
Covered Lines:	1004
Relevant Lines:	1078

---

💛 - Coveralls

[bmish]

I'm going to merge this now for a forthcoming minor release. I'm open to receiving and addressing feedback after the merge.

[bmish]

This was necessary so that consumers who use our flat config in their eslint.config.ts has the right RuleEntry type instead of just generic string.

[Krinkle]

This is awesome, thank you @bmish!