chore: use eslint-plugin-i

[bluwy]

Description

Use eslint-plugin-i instead of eslint-plugin-import to remove a bunch of useless polyfill packages.

https://github.com/un-es/eslint-plugin-i is an active fork of eslint-plugin-import.

Additional context

I noticed the license file is updated on build after some recent deps update, which adds new polyfill packages licenses. Trying to remove the useless polyfill packages step-by-step.

NOTE: @eslint-types/import package now doesn't work for eslint-plugin-i, but I left it as is until it has a new package in the future we could use. cc @Shinigami92

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[Shinigami92]

@eslint-types/import can safely removed. It only adds type safety and documentation for rules, extends and so on in eslint config

Either eslint-plugin-i need to ship support for eslint-define-config from their side, or they should provide a reason why they can't ship support from their side and so I need to add support from @eslint-types/i. The later one is less preferred.

[bluwy]

eslint-plugin-i is a plain fork of eslint-plugin-import, so I guess they share the same reason. But I'm not really familiar with this territory of eslint in general.