Hopefully this will fix the occasional failures we were seeing in the room directory.

The problem was that events are not necessarily persisted (and `current_state_delta_stream` updated) in the same order as their stream_id. So for instance current_state_delta 9 might be persisted *before* current_state_delta 8. Then, when the room stats saw stream_id 9, it assumed it had done everything up to 9, and never came back to do stream_id 8.

We can solve this easily by only processing up to the stream_id where we know all events have been persisted.

you can't plausibly ALTER TABLE in sqlite, so we create the new table with the
right schema to start with.

It turns out that _local_membership_update doesn't run when you join a new, remote room. It only runs if you're joining a room that your server already knows about. This would explain #4703 and #5295 and why the transfer would work in testing and some rooms, but not others. This would especially hit single-user homeservers.

The check has been moved to right after the room has been joined, and works much more reliably. (Though it may still be a bit awkward of a place).

Fix inserting bytes as text in `censor_redactions`

Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

Factor out backgroung updates

Fixes #6109

* Remove unused public room list timeout param

* Add changelog

* Fix /federation/v1/state for recent room versions

Turns out this endpoint was completely broken for v3 rooms. Hopefully this
re-signing code is irrelevant nowadays anyway.

Don't regenerate numeric user ID if registration fails.

This prevents us logging "Responding to media request with responder %s".

Fix unique_user_filter_index schema update

Cache room membership lookups in _get_joined_users_from_context

Don't 500 when trying to exchange a revoked 3PID invite