Instead of relying on the mess of downloading a tarball release, use the
nicely packaged webapp.

The emails where not delivered to anyway nor do they continue useful
information. Log output is now viewable in journalctl and some hardening
is applied.

This reverts commit bcfe1cbd.

Broken.

    fatal: [matrix.archlinux.org]: FAILED! => {"changed": false, "msg": "value of state must be one of: present, absent, latest, forcereinstall, got: 1.14.0"}

Archivetools syncs from kitchensink_tier1 for some reason, to create the
repository and stuff.

Set up the postfix relayhost functionality correctly.

gemini

pubkey should be on one line and should not contain enters

In preparation of the move to gemini make it already run the
archive.archlinux.org frontend and the archive-uploader. So the
migration is done in steps.

The web frontend of the archive has been moved to gemini in preparation
of the migrating of the repos to gemini. Later when dbscripts is moved
to gemini the full role is run.

This seems more proper as default.target is not a real target that
services should require. multi-user.target is the sensible default
for such services.

Rename the variable so it's more clear it's for the retro website.

Update it with the addition of gemini, monitoring and other servers.

Btrfs by default has a pretty stupid algorithm that checks for whether a file is
compressable or not. In practice this algorithm is pretty slow in my tests and
just directly passing the file to zstd is faster. I'm running compress-force=zstd
on all my machines now and it seems safe. Let's roll with this.

This ensures that install_arch behaves the same as common.