chore: upgrade knip

[webpro]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

After adding support for exports.key = value (next to module.exports), Knip's integration tests against ESLint failed, since the ESLint codebase contains a few instances of exports (without module.) that are written in the ambiguous CommonJS style that Knip considers an issue (wrote about this when introducing Knip here: https://knip.dev/guides/commonjs).

What changes did you make? (Give an overview)

• Upgrade Knip to the version that adds supports for exports.key = value syntax
• Refactored the instances that are ambiguous in terms of default vs named imports/exports.

Is there anything you'd like reviewers to focus on?

Not really, but for the sake of completeness:

• The PR were Knip was introduced to this repo: chore: Introduce Knip #18005
• The Knip issue were this feature was requested: commonjs unused module.exports detected vs exports not detected webpro/knip#580

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	533fcd2
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/660f953953811c00081d1cb3

[mdjermanovic]

LGTM, thanks!