… for Ansible to install and enable it.

… make sure Ansible actually runs the new task.

…this, the task will fail)

…st and Admin workstations.

… loading.

…with a button opening the wrong interface.

This explicitly adds support for GNOME Shell 3.38,
and corrects some issues with the gettext system
to make translations work correctly.

It also wraps the user-facing strings in gettext
calls for said translations.

… extension as the SecureDrop Menu.

…NOME Shell extension

In the original (since lost) 1cfd35b, we tried to treat the GNOME Shell
extension as a separate "securedrop/extension" Weblate component with
its own "translate-extension" command, replicating both
"--extract-update" and "--compile" modes.

In f3d3f04, we tried to treat the GNOME Shell extension as an extension
(sorry) of the main "securedrop/securedrop" component, taking advantage
of Babel's mapping feature to parse the ".js.in" file as JavaScript.

Here we harmonize the two approaches.  "translate-desktop
--extract-update" is now a two-step process, first via Babel over the
".js.in" JavaScript file, then as usual via xgettext over the ".j2.in"
desktop templates.  (This is logically reversed, but Babel appears to
have no equivalent of xgettext's appending "--join-existing" mode.)
"translate-desktop --compile" similarly does two passes with msgfmt,
first to create the standard gettext directory layout and then to update
the desktop templates.

NB. We also add "msgmerge --no-fuzzy-matching" after #6772, which
required rebasing from "develop".

In Ansible idiom, the "locale" tree should come from the role's files
rather than its template, which would simplify the path reference.
However, it's generated by "i18n_tool.py", which shouldn't be concerned
with the surrounding Ansible layout.