[#1560] Restricted AP- & OStatus-related routes for non-federating instances

Closes #1560

See merge request pleroma/pleroma!2235

rip out fetch_initial_posts

Closes #1422 and #1595

See merge request pleroma/pleroma!2297

Wasn't in the test suite otherwise

rate limiter: disable based on if remote ip was found, not on if the plug was enabled

Closes #1620

See merge request pleroma/pleroma!2296

Every time someone tries to use it, it goes mad and tries to scrape the
entire fediverse for no visible reason, it's better to just remove it
than continue shipping it in it's current state.

idea acked by lain and feld on irc

Closes #1595 #1422

pleroma_api_controller.ex: Improve conversations error reporting

See merge request pleroma/pleroma!2264

Related: https://git.pleroma.social/pleroma/pleroma/issues/1594

# Conflicts:
#	lib/pleroma/plugs/static_fe_plug.ex

Update AdminFE

See merge request pleroma/pleroma!2292

Fix Cache Control headers on media

See merge request pleroma/pleroma!2295

auth_controller.ex: Add admin scope to MastoFE

See merge request pleroma/pleroma!2256

pleroma_api.md: direct_conversation_id vs. conversation_id

See merge request pleroma/pleroma!2263

Fix hashtags WebSocket streaming

Closes #1593

See merge request pleroma/pleroma!2294

Fix static FE plug to handle missing Accept header.

See merge request pleroma/pleroma!2260

The current rate limiter disable logic won't trigger when the remote ip
is not forwarded, only when the remoteip plug is not enabled, which is
not the case on most instances since it's enabled by default. This
changes the behavior to warn and disable  when the remote ip was not forwarded,
even if the RemoteIP plug is enabled.

Also closes #1620

Formatting: Do not use \n and prefer <br> instead

Closes #1374 and #1375

See merge request pleroma/pleroma!2204

Revert "Set better Cache-Control header for static content"

Closes #1613

See merge request pleroma/pleroma!2290

It moves bbcode to bbcode_pleroma as the former is owned by kaniini
and transfering ownership wasn't done in a timely manner.

Closes: https://git.pleroma.social/pleroma/pleroma/issues/1374
Closes: https://git.pleroma.social/pleroma/pleroma/issues/1375

Exclude private and direct statuses visible to the admin when using godmode

Closes #1599

See merge request pleroma/pleroma!2272

# Conflicts:
#	test/web/activity_pub/activity_pub_controller_test.exs

CLI_tasks/user.md: Fix `pleroma.user new` documentation

Closes #1621

See merge request pleroma/pleroma!2286

Allow account registration without an email

See merge request pleroma/pleroma!2246

Merging default release config on app start

Closes #1610

See merge request pleroma/pleroma!2288

Relay list shows hosts without accepted follow

See merge request pleroma/pleroma!2240

On furher investigation it seems like all that did was cause unintuitive
behavior. The emoji request flood that was the reason for introducing it
isn't really that big of a deal either, since Plug.Static only needs to
read file modification time and size to determine the ETag.

Closes #1613

installation/otp_en.md: Fix pleroma.nginx target [deb]

See merge request pleroma/pleroma!2280

- [] for options
- <> for mandatory arguments
- foo ... when foo can be repeated

[ci skip]

Closes: https://git.pleroma.social/pleroma/pleroma/issues/1621

[ci skip]

static-fe.css: Restore from before a65ee8ea

See merge request pleroma/pleroma!2284

Related: https://git.pleroma.social/pleroma/pleroma/issues/1616

Fix enforcement of character limits

Closes #1618

See merge request pleroma/pleroma!2283

Needs to be backported to stable.

Related: https://git.pleroma.social/pleroma/pleroma-support/issues/29