Port compatibility changes from 8f5fdab5bf to glitch-soc

Port 46061dc041 to glitch-soc

Port 7403e5d306 to glitch-soc

Port 05f90e3695 to glitch-soc

Port c9cbb8de70 to glitch-soc

Port 25f6f41052 to glitch-soc

Port cdb101340a to glitch-soc,
but without dropping support for regexp filters yet.

So far, glitch-soc used history.length to decide whether to call `goBack()` or
go to / in order to not leave the webUI. This made clicking the “Back” button
go to the “Getting started” column instead of going back in the browser's
history when such an action would leave the web UI, but also when:
- The WebUI is refreshed (F5)
- A tab is restored
- The history length reaches its maximum (e.g., 50 in Firefox)

This commit fixes these shortcomings by checking `window.history.state`.
Indeed, we only want to go back in the browser's history when the current
location has been reached from within the WebUI, which only happens via
`pushState` as far as I know. Since browser store the serialized state in
the browser history, this also survives page reload and session restoration.

Port cbf97c03bb to glitch-soc

Port 9a1a55ce52 to glitch-soc

Unlike boosts and like, there is no confirmation dialog as misclicking
can be recovered without another user seeing it.

Port 913a38111f to glitch-soc

Port 5131012505 to glitch

Consistency, eslint, etc.

This gets wide view, auto layout, and navbar-under-mobile working again.

* Show confirmation dialog on leaving WebUI while composing

Currently, Back button and Back hotkey can cause leaving from WebUI, as well as browser's back button. Users may hit those buttons accidentally, and their composing text will be lost.

So this prevents it by showing confirmation dialog from `onbeforeunload` event.

* Fix message and comments

* Refactor initial state: "me"

* remove "me" from reducers/meta.js

* Lists all Direct statuses you've sent and received
* Displayed in Getting Started
* Streaming server support for direct TL

Because alt+n is a way to enter some kinda letter on some keyboard

AZERTY layouts require pressing shift to press a number at all, so
it triggers a column switch even when simply typing numbers in
textarea

* Fix #2102 - Implement hotkeys

Hotkeys on status list:

- r to reply
- m to mention author
- f to favourite
- b to boost
- enter to open status
- p to open author's profile
- up or k to move up in the list
- down or j to move down in the list
- 1-9 to focus a status in one of the columns
- n to focus the compose textarea
- alt+n to start a brand new toot
- backspace to navigate back

* Add navigational hotkeys

The key g followed by:

- s: start
- h: home
- n: notifications
- l: local timeline
- t: federated timeline
- f: favourites
- u: own profile
- p: pinned toots
- b: blocked users
- m: muted users

* Add hotkey for focusing search, make escape un-focus compose/search

* Fix focusing notifications column, fix hotkeys in compose textarea

* Upgrade to React 16.0.0

* Disable some uncritical tests while chai-enzyme remains incompatible

* Make dropdowns render into portal, expand animation

* Improve actions modal style

* Add Pinned_toot_section

* Fix add frozen_string_literal

* Fix delete no need controller and tests

* Fix replace query strings to axios params

* Fix change value to accountId and disabling more button