Signed-off-by: Thibaut Girka <thib@sitedethib.com>

Port front-end changes from 6d44f2441b to glitch-soc

Port 967e419f8f to glitch-soc

Signed-off-by: Thibaut Girka <thib@sitedethib.com>

Port ad510db3a1 to glitch-soc

Port 56f29c38b6 to glitch-soc

Port 379c3e237f to glitch-soc, but changing
the 5 limit to 10, since that's what we had previously

Port JS from 69141dca26 to glitch-soc

Fixes #956

Port 80f0910e21 to glitch-soc

Port 7477db7268 to glitch-soc

Port front-end parts of 3a92885a86 to glitch-soc

Port be1c634b2b to glitch-soc

Port fd128b9c7a to glitch-soc

Port 4407f07014 to glitch-soc

Port 26c56d0c10 to glitch-soc

Port front-end parts of 230a012f00 to glitch-soc

Also includes 9e45b051cf

Port 750c67660d to glitch-soc

Port missing parts from 2c51bc0ca5 to glitch-soc

Port 4c03e05a4e to glitch-soc

This introduces new requirements in the API:

  `/api/v1/timelines/tag/:tag` now accepts new params: `any`, `all` and `none`
  It now returns status matching tag :tag or any of the :any, provided that
  they also include all tags in `all` and none of `none`.

Port 4f42238c29 to glitch-soc

Port 06252ec71e to glitch-soc

Port 7403e5d306 to glitch-soc

Port 13dce12665 to glitch-soc

The `hasMore` property of timelines in redux store was set whenever an API
request returned only one page of results, *even* if the query only requested
newer statuses (using `since_id`), causing `hasMore` to be incorrectly set to
false whenever fetching new toots in a timeline, which happens each time
an account's timeline or media gallery is visited.

Port 023fe5181b to glitch-soc

Port 3cecf3e5b9 to glitch-soc

Port dd00cd19d2 to glitch-soc

Port bb5558de62 to glitch-soc

Port 9c38c5daa3 to glitch-soc

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.

Port 025fbb8285 to glitch-soc

Port f9b23a5d62 to glitch-soc

Port 460e380d38 to glitch-soc

Port Mastodon's hashtag stats thing to glitch-soc.
This doesn't change how hashtags are ordered, and doesn't add a trending
hashtags section, but it does change how hashtag searches are rendered,
displaying a trend line alongside each hashtag.