Apparently flake8 v3 puts the error on a different line to v2. Easiest way to
make sure that happens is by putting the whole statement on one line :)

Apparently flake8 v3 doesn't like trailing comments on config settings.

Also remove the pep8 config, which didn't work (because it was missing W503)
and duplicated the flake8 config. We don't use pep8 on its own, so the config
was duplicative.

Implement updates and deletes for devices

You can update the displayname of devices now.

Log the hostname the reCAPTCHA was completed on

Create index on user_ips in the background

Slightly saner logging for unittests

1. Give the handler used for logging in unit tests a formatter, so that the
output is slightly more meaningful

2. Log some synapse.storage stuff, because it's useful.

A bit of a cleanup for background_updates, and make sure that the real
background updates have run before we start the unit tests, so that they don't
interfere with the tests.

This could be useful information to have in the logs. Also comment about how & why we don't verify the hostname.

user_ips is kinda big, so really we want to add the index in the background
once we're running. Replace the schema delta with one which will do that.

I've done this in a way that's reasonably easy to reuse as there a few other
indexes I need, and I don't suppose they will be the last.

make /devices return a list

Turns out I specced this to return a list of devices rather than a dict of them

Implement GET /device/{deviceId}

Preserve device_id from first call to /register

GET /devices endpoint

device_id may only be passed in the first call to /register, so make sure we
fish it out of the register `params` rather than the body of the final call.

(pick up PR #938 in the hope of fixing the UTs)

Record device_id in client_ips

Register a device_id in the /v2/register flow.

implement a GET /devices endpoint which lists all of the user's devices.

It also returns the last IP where we saw that device, so there is some dancing
to fish that out of the user_ips table.

Record the device_id when we add a client ip; it's somewhat redundant as we
could get it via the access_token, but it will make querying rather easier.

Fix some more comments on some things

This doesn't cover *all* of the registration flows, but it does cover the most
common ones: in particular: shared_secret registration, appservice
registration, and normal user/pass registration.

Pull device_id from the registration parameters. Register the device in the
devices table. Associate the device with the returned access and refresh
tokens. Profit.