chore: add i18next-plugin-eslint resource

[PBK-B]

Description

This PR adds a new community resource entry to the documentation:

• Added an "Other resources" section in README.md
• Added a link to i18next-plugin-eslint, which provides the same set of ESLint rules as i18next-cli lint

This change is based on the commits currently ahead of main:

• c096319 — chore: add i18next-plugin-eslint resource

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

• only relevant documentation part is changed (make a diff before you submit the PR)
• motivation/reason is provided
• commit message and code follows the Developer's Certification of Origin

TBR; @adrai

[adrai]

Interesting, but why does this relate to i18next-cli?
Seems your eslint plugin does not use i18next-cli...

[PBK-B]

@adrai yes, the code of i18next-cli is not reused in the previous stage, in which the no-literal-string check rule will be subject to i18next-cli lint.

[PBK-B]

I thought i18next-cli was a new ecosystem, and it also made sense to build other technology stack tools around it?
listing these resources in the document may help users quickly access to i18next in their current workflow.

[PBK-B]

If you are worried about the code and the controllable risk, the relevant warehouses and npm packages related to i18next under my account can be migrated to the i18next organization at any time. You can contact me at any time to complete the work. (or i18next has its own eslint rules for use, which can be completely removed)

[adrai]

What I mean is, since your eslint plugin is not using i18next-cli, it maybe fits better to be mentioned here? https://www.i18next.com/overview/plugins-and-utils#utils

So I suggest you close this PR and open a new one for the eslint plugin to be listed there.

[PBK-B]

@adrai OK, thank you. I'll deal with this later.