Exploring alternative resolutions for the notice compatibility routes

As some may know, we have had a strong controversy over a particular MR that added "notice compatibility routes". For this reason, we should discuss and act on an alternative solution before version 2.5.0 releases. Here's some ideas:

• We can make the routes optional using a Pleroma configuration setting. I made an implementation in !3579 (closed). However, this does come with a downside, which is that instance admins would have to restart the server if they changed that setting.
• We can remove the implementation and document ways to achieve the same thing with reverse proxies. I believe @debula might know how to do this for Pleroma instances that have Soapbox as their primary frontend.

If there is any better ideas for resolving this, we are open to them.

BEFORE RESPONDING, PLEASE READ THE FOLLOWING:

Even though these are in early stages, we expect everyone that intends to be involved in this discussion to abide by our guidelines on acceptable behavior.