Move things out of SQLBaseStore

This reverts commit 00f0d675.

Its going to get removed soon, so lets not make merge conflicts.

Fix issue #6406 parameter mismatch

Filter state, events_before and events_after in /context requests

Merge branch 'babolivier/context_filters' of github.com:matrix-org/synapse into babolivier/context_filters

Co-Authored-By: Erik Johnston <erik@matrix.org>

make cross signing signature index non-unique

Ensure that the the default settings for the room directory are that the it is hidden from public view by default. 

(hopefully)

... and deobfuscate the relevant bit of code.

Signed-off-by: Syam G Krishnan <syamgk@gmail.com>

Signed-off-by: Syam G Krishnan <syamgk01@gmail.com>

Implement part [MSC2228](https://github.com/matrix-org/matrix-doc/pull/2228). The parts that differ are:

* the feature is hidden behind a configuration flag (`enable_ephemeral_messages`)
* self-destruction doesn't happen for state events
* only implement support for the `m.self_destruct_after` field (not the `m.self_destruct` one)
* doesn't send synthetic redactions to clients because for this specific case we consider the clients to be able to destroy an event themselves, instead we just censor it (by pruning its JSON) in the database

Signed-Off-By: Filip Štědronský <g@regnarg.cz>

Implement MSC 2367 - Membership Reasons

Discard retention policies when retrieving state

Purge jobs don't delete the latest event in a room in order to keep the forward extremity and not break the room. On the other hand, get_state_events, when given an at_token argument calls filter_events_for_client to know if the user can see the event that matches that (sync) token. That function uses the retention policies of the events it's given to filter out those that are too old from a client's view.

Some clients, such as Riot, when loading a room, request the list of members for the latest sync token it knows about, and get confused to the point of refusing to send any message if the server tells it that it can't get that information. This can happen very easily with the message retention feature turned on and a room with low activity so that the last event sent becomes too old according to the room's retention policy.

An easy and clean fix for that issue is to discard the room's retention policies when retrieving state.