Rewrite this so that it doesn't hammer the database.

since we're pulling everything out of KeyStore anyway, we may as well simplify
it.

There's no point in collecting a merged dict of keys: it is sufficient to
consider just the new keys which have been fetched by the most recent
key_fetch_fns.

These have been unused since #4120, and with the demise of perspectives, it is
unlikely that they will ever be used again.

add context to phonehome stats

Fix from_server buglet in get_keys_from_perspectives

Tables dropped: 
 * application_services, 
 * application_services_regex, 
 * transaction_id_to_pdu, 
 * stats_reporting
 * current_state_resets
 * event_content_hashes
 * event_destinations
 * event_edge_hashes
 * event_signatures
 * feedback
 * room_hosts
 * state_forward_extremities

make sure we store the name of the server the keys came from, rather than the
origin server, after doing a fetch-from-perspectives.

Cleanups in the Keyring

It's easier to check it in the caller than to complicate the interface with an
extra param.

Make this just return the key dict, rather than a single-entry dict mapping the
server name to the key dict. It's easy for the caller to get the server name
from from the response object anyway.

* rewrite & simplify

* changelog

* cleanup potential sql injection

Add delete group admin API

Prevent kick events from succeeding if the user is not currently in the room.

* Do not double encode fallback redirect URL

Signed-off-by: Marcel Fabian Krüger <zauguin@gmail.com>

Fix issue #4596

Correct default POSTGRES_USER in Docker README

Make synapse_port_db --curses work with Python 3.
Signed-off-by: Anders Jensen-Waud <anders@jensenwaud.com>

This is a bit fiddly due to the keyring doing weird things with logcontexts.

Remove presence list support as per MSC 1819

Implement MSC1915 - 3PID unbind APIs

Make starting pushers faster during start up

Transfers the m.room.related_groups state event on room upgrade.

As requested by @andrewshadura

We start all pushers on start up and immediately start a background
process to fetch push to send. This makes start up incredibly painful
when dealing with many pushers.

Instead, let's do a quick fast DB check to see if there *may* be push to
send and only start the background processes for those pushers. We also
stagger starting up and doing those checks so that we don't try and
handle all pushers at once.

Hopefully this time we really will fix #4422.

We need to make sure that the cache on
`get_rooms_for_user_with_stream_ordering` is invalidated *before* the
SyncHandler is notified for the new events, and we can now do so reliably via
the `events` stream.