add Pennsylvania Dutch to languages

See merge request pleroma/pleroma-fe!1935

Translations update from Pleroma Weblate

See merge request pleroma/pleroma-fe!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 pleroma/pleroma-fe!1934

2.7.1 fixes

See merge request pleroma/pleroma-fe!1933

Simplify the OAuth client_name

See merge request pleroma/pleroma-fe!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

Release 2.7.0

See merge request !1928