Loki v2.4.0 introduced a common config section[1][2] making the config
much smaller and better defaults.

So stripped loki.yaml down, removed options where the default is "good
enough" and tweaked retention settings per the upgrade notes[3].

So the config should basically be the example loki.yaml[4] + compactor,
retention enabled and a few tweaks (ex: compress chunks with zstd).

[1] https://github.com/grafana/loki/releases/tag/v2.4.0
[2] https://grafana.com/docs/loki/latest/configuration/#common_config
[3] https://grafana.com/docs/loki/latest/upgrading/#the-single-binary-no-longer-runs-a-table-manager
[4] https://github.com/grafana/loki/blob/v2.4.0/cmd/loki/loki-local-config.yaml

Signed-off-by: Morten Linderud <morten@linderud.pw>

[1] aurweb!233

This reverts commit 5c4ff7af.

The account migration is done, so offsite backups can be re-enabled.

New username; separate and longer account manager + storage passwords.

Also, have to use --remote-path=borg1 when interacting with rsync.net.

Increase default time range from 90 days to 6 months.

rsync.net is about to migrate us to a new username/hostname pair.

This was a regression which has been fixed upstream.

This reverts commit 67e7677e.

We're no longer allowed to reserve formerly used namespaces.

Grafana v8.2.0 added support for Prometheus's Alertmanager[1] which can
be used with the Unified Alerting added in v8.0.0[2].

[1] https://github.com/grafana/grafana/releases/tag/v8.2.0
[2] https://grafana.com/blog/2021/06/08/grafana-8.0-unified-grafana-and-prometheus-alerts-live-streaming-new-visualizations-and-more/

Mostly changes from Grafana v8.0[1].

[1] https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v8-0/

The security tracker is not compatible yet with the new sqlalchemy, use
the old version in our repos

Useful for mail.archlinux.org where this setting doesn't matter since we
force the SSH command to passwd and zsh was removed as part of the tools
cleanup effort recently (stops shadow.service from complaining about zsh
missing).

sort + groupby fanciness by @klausenbusk.

A string is always "true"[1].

[1] https://stackoverflow.com/a/34868470

Fix #392