LIVE-1928 LIVE-1776 - Add Spanish (ES) and Chinese (ZH) to pushed languages

[ofreyssinet-ledger]

With this change, we add more languages (Chinese and Spanish) to the list that makes it easy for existing users and new users to switch to their OS language:

• New users get that language by default when first launching LLD.
• Existing users that use the app in another language (english typically) get prompted with a modal telling them that their OS language is available.

🦒 Context (issues, jira)

LIVE-1928

💻 Description / Demo (image or video)

new users:

https://user-images.githubusercontent.com/91890529/164006563-0eef5118-83bf-470c-87e0-42aec001b951.mov

existing users (simulating "existing user" by doing a 1st start with the OS language in English and then after changing the OS language to Spanish, restarting LL):

https://user-images.githubusercontent.com/91890529/164007283-2bd6bb7e-9bfa-4392-b83a-03a0fddcd92f.mov

🖤 Expectations to reach

• Discoverability for new users (fully supported languages):

  1. Uninstall LL
  2. Switch OS language to Spanish or Chinese (fully supported languages)
  3. Install LL, launch it
  4. LL should be in the system's language

• Discoverability for existing users

  1. Uninstall LL
  2. Switch OS language to English
  3. Install LL, launch it, go through onboarding
  4. Quit LL, switch OS language to Spanish or Chinese
  5. Launch LL
  6. LL should prompt a dialogue asking the user to switch the language to the OS language

PR must pass CI, rebase develop if conflicts. Thanks!

• on QA: at least one of these two checkboxes must be checked:
  • [x] a specific test planned is defined on Jira
  • [ ] this PR is covered by automatic UI test
• on delivery: at least one of these two checkboxes must be checked:
  • [ ] Option 1: no impact: The changes of this PR have ZERO impact on the userland (invisible for users)
  • [x] Option 2: atomic delivery: the changes is atomic and complete (no partial delivery)

[github-actions[bot]]

Thanks for your contribution. To be able to merge in develop branch, you need to:

• [x] pass the CI
• [ ] if needed, run /generate-screenshots
• [x] have a dev review
• [x] have a QA review

• [ ] if needed, /upgrade-llc

  Why /generate-screenshots ?

  If your PR contains UI related changes, it might be necessary to regenerate screenshots.

  Why /upgrade-llc ?

  If your PR requires an update to the ledger-live-common library, once the PR is merged on develop on ledger-live-common side, you need to run /upgrade-llc to switch back to ledger-live-common@develop here before merging.

[github-actions[bot]]

Coverage report

St.:grey_question:	Category	Percentage	Covered / Total
🔴	Statements	23.46%	38/162
🔴	Branches	20.51%	8/39
🔴	Functions	3.64%	2/55
🔴	Lines	24.16%	36/149

Test suite run success

2 tests passing in 2 suites.

Report generated by 🧪jest coverage report action from 3e6bb3f2000f887b83e3872de6ac732597005478

[ofreyssinet-ledger]

/generate-screenshots

[github-actions[bot]]

Generating new screenshots

[LFBarreto]

Tested on linux + spanish: new users flow :heavy_check_mark: existing users :heavy_check_mark: