Update prefixer settings and required gitlab runner tags

See merge request !1942

Support displaying time in absolute format

See merge request !1938

This adds two config items: useAbsoluteTimeFormat (boolean) and
absoluteTimeFormatMinAge (string, number + unit ('d'|'h'|'m'|'s')).

When `useAbsoluteTimeFormat` is true, the Timeago component will display
absolute time if the time is at least `absoluteTimeFormatMinAge`
from now. If `longFormat` prop is true, the fully formatted time
is displayed. Otherwise, the format is determined by the `time` prop:
(1) if `time` is on the same day of now, display hour and minute;
(2) if `time` is in the same month of now, display day and hour;
(3) if `time` is in the same year of now, display month and day;
(4) otherwise, display year and month.

If it should display relative time, the format is the same as before.

add Pennsylvania Dutch to languages

See merge request !1935

Translations update from Pleroma Weblate

See merge request !1929

Currently translated at 92.0% (1098 of 1193 strings)

Translation: Pleroma/Pleroma-FE
Translate-URL: https://translate.pleroma.social/projects/pleroma/pleroma-fe/eo/

Currently translated at 57.1% (682 of 1193 strings)

Translation: Pleroma/Pleroma-FE
Translate-URL: https://translate.pleroma.social/projects/pleroma/pleroma-fe/pl/

Currently translated at 94.5% (1128 of 1193 strings)

Translation: Pleroma/Pleroma-FE
Translate-URL: https://translate.pleroma.social/projects/pleroma/pleroma-fe/fr/

Currently translated at 97.1% (1159 of 1193 strings)

Translation: Pleroma/Pleroma-FE
Translate-URL: https://translate.pleroma.social/projects/pleroma/pleroma-fe/ja_PEDANTIC/

Currently translated at 99.6% (1189 of 1193 strings)

Translation: Pleroma/Pleroma-FE
Translate-URL: https://translate.pleroma.social/projects/pleroma/pleroma-fe/zh_Hans/

Merge master back into develop

See merge request !1934

2.7.1 fixes

See merge request !1933

Simplify the OAuth client_name

See merge request !1930

Every time PleromaFE is used to login it will need to do the OAuth dance and request an app key. If the client name is not stable it will pollute the server's database with entries.

This also happens on every unauthenticated page load at the moment until #1339 is resolved

Every time PleromaFE is used to login it will need to do the OAuth dance and request an app key. If the client name is not stable it will pollute the server's database with entries.

This also happens on every unauthenticated page load at the moment until #1339 is resolved