provides tooling for interactive localization updates (option A)

[cfm]

Description

Closes #1317 by:

1. removing the l10n GitHub Actions workflow added in mechanizes continuous-localization workflow #1282;
2. renaming the Make targets extract-strings and check-strings for clarity;
3. using check-strings in CI to "lint" that the translation catalog has been updated via extract-strings; and
4. offering a Git pre-commit hook for check-strings configurable with make hooks.

How to think about this pull request

The following gist offers background considerations shared with, and for evaluating this "option A" pull request against, "option B" #1348:

https://gist.github.com/cfm/d3173206f55d7e44152928fcfd215031

Test Plan

1. Change a _()-wrapped source string and commit it
2. Push to testing branch like 1347-cfm-testing (where cfm is your GitHub username ;-)
3. Confirm that test-buster fails on make check-strings with the following error message:

   Translation catalog is out of date. Please run "make extract-strings" and commit the changes.

4. Run make hooks (or rerun make venv or your platform-appropriate variant)
5. Try to git commit --amend and confirm that the pre-commit hook fails on make check-strings as above
6. Run make extract-strings
7. Retry git commit --amend and confirm that the commit succeeds
8. git push -f to your testing branch
9. Confirm that test-buster passes

Checklist

• Remove (option A) from title and close provides tooling for interactive localization updates #1348 without merging

If these changes modify code paths involving cryptography, the opening of files in VMs or network (via the RPC service) traffic, Qubes testing in the staging environment is required. For fine tuning of the graphical user interface, testing in any environment in Qubes is required. Please check as applicable:

• I have tested these changes in the appropriate Qubes environment
• I do not have an appropriate Qubes OS workstation set up (the reviewer will need to test these changes)
• These changes should not need testing in Qubes

If these changes add or remove files other than client code, the AppArmor profile may need to be updated. Please check as applicable:

• I have updated the AppArmor profile
• No update to the AppArmor profile is required for these changes
• I don't know and would appreciate guidance

If these changes modify the database schema, you should include a database migration. Please check as applicable:

• I have written a migration and upgraded a test database based on main and confirmed that the migration applies cleanly
• I have written a migration but have not upgraded a test database based on main and would like the reviewer to do so
• I need help writing a database migration
• No database schema changes are needed

[cfm]

Closing in favor of #1348 per #1317 (comment).