I moved the rest of scope "/api/v1/pleroma/admin" down because otherwise there's conflict between the endpoints `get("/users/:nickname"` and `get("/users/invites"`.

I made sure that users who can set tags, can't set tags starting with "moderation_tag:". Otherwise they can easily give themselves, or any one else, any of the moderation rights.

This was also the last of priviledged staff, so I removed traces from that as well. See <pleroma/pleroma!3578 (diffs)>.

Everything to do with credentials is added under this tag
I also fixed a bug that happened when someone had multiple tags

I also did some refactoring for the tests where I felt made sense.

I redid the report grouping, but now TTD

I also added the other groups in the router already, but haven't moved things around yet

I made the module to check for a user tag more general.

This is a first step to have more fine-grained control on what a staff member can access.

In this commit I only imlemented report triage and I only changed things for the admin-api.
Note that in case of reports, there's also report-notifications being generated. This also needs to be adapted, but isn't done in this commit yet.

Also note that someone still needs to be staff member. Having the tag is required, but not enough.

Translate backend-rendered pages

See merge request !3634

Update Caddyfile to Caddy v2

Closes #2764

See merge request !3641

Delete report notifs when demoting from superuser

Closes #2840

See merge request !3642

mix: Check `.git` presence

See merge request !3638

Use patern matching to see if someone was superuser before

Fix test get_user_apps/1

See merge request !3636

Copyright bump for 2022

See merge request !3593

When someone isn't a superuser any more, they shouldn't see the reporsts any more either.
Here we delete the report notifications from a user when that user gets updated from being a superuser to a non-superuser.

elixir gettext current does not fully support fallback to another language [0].
But it might in the future. We adapt it so that all languages in Accept-Language
headers are received by Pleroma.Web.Gettext. User.languages is now a comma-separated
list.

[0]: https://github.com/elixir-gettext/gettext/issues/303

For an example, here, zh is not supported, but zh_Hans and zh_Hant
are. If the user asks for zh, we should choose a variant for them
instead of fallbacking to default.

Some browsers (e.g. Firefox) does not allow users to customize
their language codes. For example, there is no zh-Hans, but only
zh, zh-CN, zh-TW, zh-HK, etc. This provides a workaround for
those users suffering from bad design decisions.

Revert "Merge branch 'revert/notice-routes' into 'develop'"

See merge request !3639

This reverts merge request !3576