Fix #9057

Follow-up to e45a6edd6574c86409333cc64f9fb87e1b0a196e, fixes inconsistencies
in glitch-soc behavior.

Fix #9034

Reminder: Suggestions were added in #7918 and are based on who you
interact with who you do not follow. E.g. if you boost someone a lot
from seeing other people's boosts of that person, it makes sense you
might be interested in following the original source; or if you reply
to someone a lot, maybe you'd want to follow them

Each suggestion can be dismissed

This reverts commit c7e9f9ff1e.

Port 7861c5f108 to glitch-soc

Port bebe8ec887 to glitch-soc

Port c73864c137 to glitch-soc

Port 3a157210c8 to glitch-soc

Port bf58461d36 to glitch-soc

Port 25f9ead041 to glitch-soc

Port 029943d59b to glitch-soc

Port 065b39e7a4 to glitch-soc

Port 301cbcc980 to glitch-soc

Port 65b3804a6c to glitch-soc

Port d35801aaa2 to glitch-soc

Port f8c1b32541 to glitch-soc

Port efd09e2ebb to glitch-soc

Port b972478812 to glitch-soc

Revert server-side part of 87fdd139b8

* RTL: remove blank character inside bdi

* Update app/javascript/mastodon/components/display_name.js

Co-Authored-By: mabkenar <ampbox@gmail.com>

Fixes #9045

* RTL: fix admin account avatar margin in about page

* fix code style

This uses the same logic as the status icons in the glitch flavor.

Fixes #395

Instead of leaving the toot body blank, it replaces it with a single “.” in
order for the fold/unfold CW behavior to not look *too* weird on upstream
Mastodon. Note that this does not fix upstream's CW-dropping behavior, as
that is decided at the time the toot is posted, not received.

* Fix position of the domain label

* Fix position of the domain label for RTL

- Fix color mismatch of linear gradient which assigned to "::after" pseudo class

Indeed, when the “Always enable the Content Warning field” setting is enabled,
sending a content-less toot with a CW would move the CW to the toot's content
and leave the toot not marked as sensitive.

* Add "disable" button to report screen

* i18n-tasks remove-unused

* Do not show "limited" visibility in default visibility preference

Fix regression from #8950

* Fix code style issue

* Add silent column to mentions

* Save silent mentions in ActivityPub Create handler and optimize it

Move networking calls out of the database transaction

* Add "limited" visibility level masked as "private" in the API

Unlike DMs, limited statuses are pushed into home feeds. The access
control rules between direct and limited statuses is almost the same,
except for counter and conversation logic

* Ensure silent column is non-null, add spec

* Ensure filters don't check silent mentions for blocks/mutes

As those are "this person is also allowed to see" rather than "this
person is involved", therefore does not warrant filtering

* Clean up code

* Use Status#active_mentions to limit returned mentions

* Fix code style issues

* Use Status#active_mentions in Notification

And remove stream_entry eager-loading from Notification

This fixes hotkeys not working when pressing the column
“back” button, for instance.

Regression from #8569