Internationalization - make language selection a user choice rather than a browser setting

[CHJESSON]

The display language for the Chorus Portal has always been tied to the language set for the browser - the suggestion would be to make this a "user preference" instead, picking from a list of supported languages.

The challenges with tying to the browser language are as follows:

1. Browser language selection is often wildly inconsistent between users, as is not often locked down by network administrators. We often find that even if a specific browser language is officially mandated, this mandate isn't always adhered to
2. The user can have a browser language set that isn't supported by Chorus, requiring a fallback to en-us. If instead the user is presented with a list of supported languages this no longer becomes an issue/consideration
3. Making language selection a user choice also means that the selected language will persist if the user switches to a different browser, e.g. from Chrome to Edge. We sometimes find that users have (say) Chrome set to "en-gb" but Edge set to "en-us"

[Karen_Hunter]

User Admin currently has a language code indicator that can be tied to the User Account ID.  Would you expect the user to change between available languages or simply enforce the preferred configuration?

BPMA-I-5

[LHua]

For our purposes, we would expect the user to be able to change between available languages