V2 Translate component

[Zasa-san]

Front end team has been working on a V2 Translate component. The aim is to remove redux dependencies from translations, so that new routes have as few dependencies from V1 as possible.

To cover in the PR we have been working on:

• Migrate the Translate component to use atoms and not redux
• Migrate the t function in the same way
• If possible, use V2 translations API data structure
• If possible, stop depending on redux for the initial state of the app
• Update translation sockets actions to update atom store and not redux
• Tests (test that atoms update via sockets, test that when you submit translations the socket even is fired?, we are not updating the translationsAtom after submitting, so consistency across the UI depends on sockets)
• Refactor (for example t has circular deps)
• API changes need to be reviewed
• Modal styles
• Cleanup
• After merging, create issue to migrate form so that we can remove the old translations endpoitns
• Modal stacking. Translate modal can be triggered by other modals. It should always sit on top of all other app elements.
• unit test for app/react/V2/api/translations/index.ts postV2

[Zasa-san]

We should check if the languages listed in /settings/languages are meant to be translatable. By default, they are not listed in the translationsV2 collection. They are currently translatable, and I understand that our system allows you to translate keys that are not present in the translationsV2 collection. I recall those not being translatable.

In any case, we need to remember that if a term is not present in the context users should still be able to translate it.