[Due for payment 2025-06-27] [Due for payment 2025-06-25] Surface more locales in LocalePicker

[roryabraham]

HOLD for #62801 decided to get going on the front-end here to add the new languages to the selector behind the staticAITranslations beta.

Design doc section: https://docs.google.com/document/d/1uj-k3riU2K6ceU2VtC-I181C-Vvp0mdOOB7IHdqUn6o/edit?tab=t.0#bookmark=id.72tnrqcmdtzi

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Triggered auto assignment to @muttmuure (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

[roryabraham]

No design or BZ help needed here. It is on a GitHub Project only for CAP SW purposes

[roryabraham]

Actually, we will most likely need design help here down the line. Because this is the issue where the translations for other languages will actually be displayed in the app. I expect we will uncover some oddities when we do that.

[trjExpensify]

@roryabraham to parallelise the work, should we have someone do the front-end work for this now and add the list of languages to the selector, behind the beta? They won't do anything right now when selected, but not harming anything either being there ready to change the language.

[roryabraham]

Sure. This is mostly done already in #56520 so I'm not sure how critical/helpful it would be to get someone else working on implementing it before the translations are ready though