handlers/room_member: fix guest access check when joining rooms

Signed-off-by: Patrik Oldsberg <patrik.oldsberg@ericsson.com>

log call paths for resolve_state_group

add logging for all the places we call resolve_state_groups. my kingdom for a backtrace that actually works.

More logging for the linearizer and for get_events

cherrypick #1744: limit total timeout for get_missing_events to 10s

Only send events that originate on this server.

Or events that are sent via the federation "send_join" API.

This should match the behaviour from before v0.18.5 and #1635 landed.

Fix propagation of bans to remote servers.

Rather than the state after then event.

Send all membership changes to the server that was affected.
This ensures that if the last member of a room on a server
was kicked or banned they get told about it.

Add more useful logging when we block fetching events

Remove fallback from get_missing_events.

get_missing_events used to fallback to fetching the missing events
individually requesting from every server in the room, one by one.e

This could be unacceptably slow, possibly causing #1732

Use the new twisted logging framework.

Hopefully adding an observer to the new framework will avoid a memory
leak https://twistedmatrix.com/trac/ticket/8164

Wrap connections in an N minute timeout to ensure they get reaped correctly

The abort() method calls loseConnection() which tries to shutdown the
TLS connection cleanly. We now call abortConnection() directly which
should promptly close both the TLS connection and the underlying TCP
connection.

I also added some TODO markers to consider cancelling the old previous
timeout rather than checking time.time(). But given how urgently we want
to get this code released I'd rather leave the existing code with the
duplicate timeouts and the time.time() check.

Add some logging for syncing to_device events

Attempt to track down the loss of to_device events
(https://github.com/vector-im/riot-web/issues/2711 etc).