Due to #5269 we may have extremities in our DB that we shouldn't have,
so lets add a cleanup task such to remove those.

When we receive a soft failed event we, correctly, *do not* update the
forward extremity table with the event. However, if we later receive an
event that references the soft failed event we then need to remove the
soft failed events prev events from the forward extremities table,
otherwise we just build up forward extremities.

Fixes #5269

Fixes #5271.

Fix docs on resetting the user directory (#5036)

Signed-off-by: Aaron Raimist <aaron@raim.ist>

Signed-off-by: Aaron Raimist <aaron@raim.ist>

Ensure that server_keys fetched via a notary server are correctly signed.

Fixes #4414.

Fix schema update for account validity

Fix logging for room stats background update

Fix error code for invalid parameter

Signed-off-by: Aaron Raimist <aaron@raim.ist>

Signed-off-by: Aaron Raimist <aaron@raim.ist>

The list of server names was redundant, since it was equivalent to the keys on
the server_to_deferred map. This reduces the number of large lists being passed
around, and has the benefit of deduplicating the entries in `wait_on`.

In particular, don't give up on the first failure.

Signed-off-by: Tulir Asokan <tulir@maunium.net>

Don't bundle aggregations with events in /sync or /events or state queries

Factor out KeyFetchers from KeyRing

Replaces DEFAULT_ROOM_VERSION constant with a method that first checks the config, then returns a hardcoded value if the option is not present.

That hardcoded value is now located in the server.py config file.

Rather than have three methods which have to have the same interface,
factor out a separate interface which is provided by three implementations.

I find it easier to grok the code this way.

This is a first step to checking that the key is valid at the required moment.

The idea here is that, rather than passing VerifyKey objects in and out of the
storage layer, we instead pass FetchKeyResult objects, which simply wrap the
VerifyKey and add a valid_until_ts field.

* Pass time_added_ms into process_v2_response

* Simplify process_v2_response

We can merge old_verify_keys into verify_keys, and reduce the number of dicts
flying around.

These were never used, and poking arbitary data into objects from other
packages seems confusing at best.

Storing server keys hammered the database a bit. This replaces the
implementation which stored a single key, with one which can do many updates at
once.

I was staring at this function trying to figure out wtf it was actually
doing. This is (hopefully) a non-functional refactor which makes it a bit
clearer.