Drop incoming events from federation for unknown rooms

Co-Authored-By: erikjohnston <erikj@jki.re>

Co-Authored-By: erikjohnston <erikj@jki.re>

Add a Content-Type header on POST requests to the federation client script

Fix noop checks when updating device keys

Fix encoding error for consent form on python3

Clients often reupload their device keys (for some reason) so its
important for the server to check for no-ops before sending out device
list update notifications.

The check is broken in python 3 due to the fact comparing bytes and
unicode always fails, and that we write bytes to the DB but get unicode
when we read.

When we receive events over federation we will need to know the room
version to be able to correctly handle them, e.g. once we start changing
event formats. Currently, we attempt to handle events in unknown rooms.

The form was rendering this as "b'01234....'".

-- richvdh

* port hash_password

* changelog

add purge_history.sh and purge_remote_media.sh scripts

Signed-off-by: Ruben Barkow <github@r.z11.de>

So people can still collect consent the old way if they want to.

fixes #4056

* Add helpers for getting prev and auth events

This is in preparation for allowing the event format to change between
room versions.

Clean up event accesses and tests

This is in preparation to refactor FrozenEvent to support different
event formats for different room versions

Fix locked upsert on device_lists_remote_cache

Fix logic error that prevented guests from seeing the privacy policy

Fix None exception in state res v2

The indexes on device_lists_remote_extremeties can be unique, and they
therefore should, to ensure that the db remains consistent.

We can rely on the application-level per-user linearizer.