Conflicts:
	bin/copy-iuks-to-rsync-server-and-verify
	wiki/src/contribute/release_process.mdwn

A recent example is the switch to GitLab: one might have forgotten to
update the “Build” step in the parallel_build_IUKs job to point at the
new remote.

v2: Use names agreed on in #17658

Conflicts:
	wiki/src/contribute/release_process.mdwn

Upgrade to Tor Browser 9.5

See merge request tails/tails!27

Update test suite for new homepage and migration to GitLab

See merge request tails/tails!25

Closes #17527

... instead of just /usr/lib/locale, otherwise we won't find the match
"ms:ID" → "ms", so no candidate and the test fails.

Honestly, the difference between these directories isn't entirely
clear to me, but the point here is just to pick a candidate that
works, and with this change the "The Unsafe Browser can be used in all
languages supported in Tails" scenario passes again so I'm happy.

GitLab closes these issues automatically only when the destination
branch is the default branch, i.e. `master` currently:
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically

I'm wondering if we should make the `stable` or `devel` branch our default
branch (assuming we merge more branches into these branches than into `master`),
but for now let's workaround the problem via documentation.

Resolve "Welcome screen help is broken following file renaming"

See merge request tails/tails!11

Bump our signing key's expiration date

Closes #17133

See merge request !17

Respectively: Lithuanian, Malay, Thai.

Fix first list (and test gitlab)

See merge request !18