Clean up community contributed locales to remove redundancies

[desi]

What is this about?

We currently have 57 locale files. 14 of these are supported by our translations partner and the rest are community supported. We currently have a couple of locales which are redundant.

• hn -- this is not an actual language code -- the translations appear to be Hindi and should be moved into the Hindi locale

• ph -- these 1759 lines of code are in Tagalog, but ph is not a recognized locale code. Someone is actively contributing to this locale, but it is likely creating confusion because right now extension lists three different locales for the same language "Filipino (fil), Pilipino (ph), Wikang Tagalog (tl)". Wikang Tagalog "tl" is the locale that is supported by our translation team -- we should determine what next steps are with regard to these 3 and combine/correct them.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [X] Engineering (needed in most cases)
• [ ] Design
• [X] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

No response

[i18nlaurel]

The only comment I have here for the hn locale is that we don't need to add these translations to the hi Hindi locale because those are actively being updated anyway. I hate to just throw away community-completed translations, but I think we should deprecate the hn locale altogether to avoid confusion since it isn't recognized by ISO. It looks like it's been over a year since the last community member contributed translations.