I18nize nav_menu's list items

[KrystalJean]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

I followed existing patterns of internationalization to translate the list items found in nav_menu.

I I18nized a total of seven list items (two of those already had translations for English, and French).
Li's include: Admin, Dashboard, Moderator Center, Create Post, Reading List, Settings, and Sign Out.

Related Tickets & Documents

This PR references issue "Internationalize Hardcoded Display Text #14888".
This will not close the issue as it is an ongoing new feature project.

QA Instructions, Screenshots, Recordings

UI accessibility concerns? none

Forem Accessibility Docs._

Added/updated tests? no

• Yes
• No, and this is why: Existing tests should suffice.
• I need help with writing tests

[Forem core team only] How will this change be communicated?

Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.

• I've updated the Developer Docs or
  Storybook (for Crayons components)
• This PR changes the Forem platform and our documentation needs to be
  updated. I have filled out the
  Changes Requested
  issue template so Community Success can help update the Admin Docs
  appropriately.
• I've updated the README or added inline documentation
• I've added an entry to
  CHANGELOG.md
• I will share this change in a Changelog
  or in a forem.dev post
• I will share this change internally with the appropriate teams
• I'm not sure how best to communicate this change and need help
• This change does not need to be communicated, and this is why not: please
  replace this line with details on why this change doesn't need to be
  shared

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[github-actions]

Thank you for opening this PR! We appreciate you!

For all pull requests coming from third-party forks we will need to
review the PR before we can process it through our CI pipelines.

A Forem Team member will review this contribution and get back to
you as soon as possible!

[msarit]

This looks great @KrystalJean! 🚀 Thank you for contributing!

I checked the translations and all looks copacetic 👌🏾

To fix the failing Travis tests, check the file cypress/integration/seededFlows/topNavigationFlows/MemberDropDownButton.spec.js.

Let me know if you need help running Cypress locally and making the changes. ❤️

[citizen428]

The test is failing because the string changed from "Reading list" to "Reading List". I'm taking the liberty to fix this myself because I want to get this PR merged because I'm in the process of doing some I18n cleanup work.

[KrystalJean]

Okay thank you @citizen428. I completely forgot about changing that capitalization.
And thank you @msarit so much for your sweet comment. Sorry I am just responding, but I have been working all day on trying to install all of the prerequisites to run this code locally, and figure out what was happening.

[citizen428]

Thanks a lot for your contribution @KrystalJean, it's much appreciated! 👏

[KrystalJean]

No problem @citizen428 . I am glad I could help, as well as gain some knowledge, and confidence.