Treat an invalid .well-known the same as an absent one

... basically, carry on and fall back to SRV etc.

Caching for invalid .well-knowns

Update federation routing logic to check .well-known before SRV

Also add a Measure block around the .well-known fetch

I can't figure out what's going on with #4422 and #4436; perhaps this will help.

* update debian installation instructions

* docs PR is docs

Fix remote invite rejections not coming down sync

remove trailing ,

This was broken in PR #4405, commit 886e5acc, where we changed remote
rejections to be outliers.

The fix is to explicitly add the leave event in when we know its an out
of band invite. We can't always add the event as if the server is/was in
the room there might be more events to send down the sync than just the
leave.

Server capabilities support

* Fix replication for room v3

We were not correctly quoting the path fragments over http replication,
which meant that it exploded when the event IDs had a slash in them

* Newsfile

* Handle listening for ACME requests on IPv6 addresses

the weird url-but-not-actually-a-url-string doesn't handle IPv6 addresses
without extra quoting. Building a string which you are about to parse again
seems like a weird choice. Let's just use listenTCP, which is consistent with
what we do elsewhere.

* Clean up the default ACME config

make it look a bit more consistent with everything else, and tweak the defaults
to listen on port 80.

* newsfile

Fix bug where synapse fails to start if no_tls set

Tiny .well-known fixes