lib-user: Setup react-i18next for Contributors components

[goplayoutside3]

Package

lib-user

Linked Issue and/or Talk Post

This is the start of a chain of translations PRs. The next one is #6554

Describe your changes

• Setup react-i18next for Contributors components

How to Review

• The expected text should display for Contributors components when lib-user is run locally, in Storybook, or as app-root pages.

Checklist

PR Creator - Please cater the checklist to fit the review needed for your code changes.
PR Reviewer - Use the checklist during your review. Each point should be checkmarked or discussed before PR approval.

General

• Tests are passing locally and on Github
• Documentation is up to date and changelog has been updated if appropriate
• You can yarn panic && yarn bootstrap or docker-compose up --build and FEM works as expected
• FEM works in all major desktop browsers: Firefox, Chrome, Edge, Safari (Use Browserstack account as needed)

New Feature

• The PR creator has listed user actions to use when testing the new feature
• Unit tests are included for the new feature
• A storybook story has been created or updated
  • Example of SlideTutorial component with docgen comments, and its story

Post-merge

• This PR adds translations keys to English dictionary(s). See guidance for pulling new keys to Lokalise here.

[coveralls]

coverage: 77.389% (+0.04%) from 77.351%
when pulling 018fdfd on translations-contributors
into 34d9680 on master.

[goplayoutside3]

@mcbouslog this is the base of multiple branches that add react-i18next to lib-user, and I'm tagging you for review of all PRs. I split up this feature to make it easier for review since these are live webpages. Please feel free to review in whichever order you prefer, and the PRs are tagged in the project board, too.

[mcbouslog]

This and related lib-user translation PRs look good. I've tested locally to make sure pages continue to load as expected. 👍 🌐

Is adding the test: "Test Language" to the storybook preview.js and related translation JSON a reasonable addition to these changes or is that something that should be in a different PR? While I noted no issues testing these changes locally, changing the language (to the "Test Language") in storybook would provide additional assurance.

[mcbouslog]

This is trivial, but if lib-classifier creates classifierI18n and lib-react-components creates zrcI18n, should this be less generic and include user or a related abbreviation?

[goplayoutside3]

That's a good point! I'll rename to libUserI18n

[goplayoutside3]

Re: Test Language dictionary - I'm going to merge this translations branch, pull the new English dictionary into Lokalise, and then have Lokalise generate a new Test Language json dictionary for me. Along with that dictionary PR, I'll enable translations in Storybook on our way to introducing localization in the app-root Next.js router.