Localization workflow improvements

[emma-sg]

• CI: Ensure generated files are up-to-date
• Local dev: Generate localization files in precommit hook?
• [ ] Linting: Ensure localization strings don't have too much HTML in them
• [ ] Linting: Ensure there are no non-localized string in HTML templates
• Integrate Weblate
• Extract strings in pull request action Localization workflow improvements #1416

[SuaYoo]

@ikreymer to investigate setting up weblate

[SuaYoo]

@ikreymer to look into deploying weblate with k8s https://docs.weblate.org/en/latest/admin/install/kubernetes.html

[SuaYoo]

Linting: Ensure there are no non-localized string in HTML templates

@emma-sg I didn't address this in #2069 but I think it's okay to start with a manual internal QA pass after translating the first language. I didn't see any existing tools that we can leverage, asked the Lit Discord channel as well.

[SuaYoo]

From #2072 it looks like we'll need to format our extracted strings XML file to match weblate's XML format (see WeblateOrg/weblate#9096)

[ikreymer]

Investigate Weblate hosting pricing / self-hosting

[SuaYoo]

@ikreymer I removed Make final decision on hosted vs self-hosted Weblate from marking this issue as complete since it focuses on localization workflow improvements, we could create a separate issue for following up with the libre trial if needed.