remove deprecated PleromaFE configuration

See merge request pleroma/pleroma!1152

Make rate limiting for Mastodon Registration API less agressive and enable it by default.

See merge request pleroma/pleroma!1154

As discussed on irc. Unlike Mastodon our web interface for registrations
is using the same APIs regular apps would be using, so 5 requests per 30
minutes per IP could hurt valid use-cases when Pleroma-FE switches to
it. Also enable the endpoint by default, it makes no sense to
have it disabled when
1. TwitterAPI endpoint is there and always enabled
2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there)

Also in this commit: minor changelog improvements.

Group def perform() together to fix the build

See merge request pleroma/pleroma!1151

gopher: fix rendering of post content (closes #895)

Closes #895

See merge request pleroma/pleroma!1150

use job queue everywhere

Closes #862

See merge request pleroma/pleroma!1142

Fix Pleroma.Config.get!/1 raising an error when value is false

See merge request pleroma/pleroma!1148

Refactoring  oauth response.

See merge request pleroma/pleroma!1149

[#694] allow users to disable their own account

See merge request pleroma/pleroma!895

Document AdminFE in changelog

See merge request pleroma/pleroma!1147

Bump Mastodon API level

See merge request pleroma/pleroma!1146

Switch to Jason over Poison

See merge request pleroma/pleroma!1145

federator modularization (outgoing)

See merge request pleroma/pleroma!1140

Features/mastoapi/2.7.0 registration

Closes #773

See merge request pleroma/pleroma!1134

[ci skip]

Make irreversible field, default to false in filters

See merge request pleroma/pleroma!1144

pleroma-fox-tan-shy.png: Add another version of pleroma-tan

See merge request pleroma/pleroma!1139

Normalize the object in `create_or_bump_for` only after ensuring the activity type is Create

Closes #874

See merge request pleroma/pleroma!1138

Add a test to ensure create_or_bump_for does not normalize objects before checking the activity type