[2754] Swap out i18n-js for react-18next

[fpena]

Please verify the following:

• yarn test jest tests pass with new tests, if relevant
• yarn lint eslint checks pass with new code, if relevant
• yarn format:check prettier checks pass with new code, if relevant
• README.md (or relevant documentation) has been updated with your changes

Describe your PR

This PR replaces the i18n-js library with i18next to enhance internationalization in the project. The migration ensures better support for translations, including improved handling of locale-specific formats, pluralization, and more efficient loading of translation resources.

Key Changes:

• Replaced all instances of i18n-js with i18next across the codebase.
• Updated translation initialization logic to use initReactI18next from the i18next library.
• Refactored translation key format: e.g., from "common.ok" to "common:ok".
• Updated all relevant unit tests reflect changes in the translation library.

Note: We will also create a cookbook recipe later that references this PR for Ignite users who want to migrate from i18n-js to i18next and are using Ignite 9.x or less.

Video

Simulator.Screen.Recording.-.iPhone.15.-.2024-09-12.at.13.44.15.mp4

[frankcalise]

Looking good!

What was the motivation behind the screen:some.key naming scheme change?

Not opposed to it, just made a bunch of extra changes because of it.

[fpena]

Looking good!

What was the motivation behind the screen:some.key naming scheme change?

Not opposed to it, just made a bunch of extra changes because of it.

@frankcalise it is the namespace separator for i18next. There's more context about it here.

[frankcalise]

Great work!