Add a hook for custom rest endpoints

Factor _AccountHandler proxy out to ModuleApi

Factor out _configure_named_resource

Let the user specify custom modules which can be used for implementing extra
endpoints.

We're going to need to use this from places that aren't password auth, so let's
move it to a proper class.

This was a bit of a code vomit, so let's factor it out to preserve some sanity

Notify auth providers on logout

Allow password_auth_providers to return a callback

Let auth providers get to the database

this got broken in the previous commit

Provide a hook by which auth providers can be notified of logouts.

... so that they have a way to record access tokens.

Let password auth providers handle arbitrary login types

Provide a hook where password auth providers can say they know about other
login types, and get passed the relevant parameters

Move access token deletion into auth handler

automatically set default displayname on register

Break dependency of auth_handler on device_handler

Remove the last vestiges of refresh_tokens

to avoid clobbering guest user displaynames on registration

Also move duplicated deactivation code into the auth handler.

I want to add some hooks when we deactivate an access token, so let's bring it
all in here so that there's somewhere to put it.

Log login requests

Carefully though, to avoid logging passwords

to avoid leaking ugly MXIDs and cluttering up the timeline with
displayname changes as well as membership joins for autojoin rooms
(e.g. the status autojoin rooms), automatically set the displayname
to match the localpart of the mxid upon registration.

Modify group room association API to allow modification of is_public

I'm going to need to make the device_handler depend on the auth_handler, so I
need to break this dependency to avoid a cycle.

It turns out that the auth_handler was only using the device_handler in one
place which was an edge case which we can more elegantly handle by throwing an
error rather than fixing it up.

Somewhat open to abuse, but also somewhat unavoidable :/

DB schema interface for password auth providers

Make the port script drop NUL values in all tables

also includes renamings to make things more consistent.

Postgres doesn't support NULs in strings so it makes the script
throw an exception and stop if any values contain \0. Drop them
with appropriate warning.

Provide an interface by which password auth providers can register db schema
files to be run at startup

Refactor some logic from LoginRestServlet into AuthHandler