At this point, after the previous step there are great chances that one is on
the devel branch, instead of the intended release one.

Merge remote-tracking branches 'origin/bugfix/7943-simplify-tor-launcher-profile-path-workaround', 'origin/bugfix/11097-tor-browser-fontconfig' and 'origin/bugfix/9896-abstract-chroot-browser-configs' into stable

Since the browsers use a different font, this image will differ from
now on and cannot be shared with Evince.

refs: #10284

Tentatively redesign new mirrors pool handling to match the fact that downloads are supposedly primarily handled via DAVE nowadays.

Refs: #10284

This reverts commit c623c8c0.

This reverts commit 450ff67c.

Tor Browser 5.5's font fingerprinting protection (enabled in #11000,
commit 2af53484) changed the GUI's fonts, breaking essentially all
tests where any browser is involved. We then enabled it for all other
browsers and Tor Launcher as well, so they are also affected.

Will-fix: #11097

I.e. also the Unsafe and I2P Browser's. The main reason is so we do
not need different images for these and the Tor browser in the
automated test suite. One may argue, though, that for the Unsafe
Browser this list of fonts would be fingerprintable, but I would be
surprised if it already isn't so due to the Tor Browser Firefox
patches.

The Tor Browser assumes that the working directory is the directory
where the browser lives (e.g. the executable). For instance, the
fonts.conf (for fontconfig) the Tor Browser uses looks for the fonts
in the "fonts" sub-directory of the current working directory. This
will fix issues with "empty boxes" as characters in the Save As/Open
dialoges.

Will-fix: #11097

No commit message