... so that it can be used on non-JSON endpoints

The metrics are now available via the request, so this is redundant and can go
away at last.

it's much neater there.

less magic

It fits quite nicely here, and opens the path to getting rid of the
"include_metrics" mess.

... which is going to make it easier to move around.

This is useful in its own right, because server.py is full of stuff; but more
importantly, I want to do some refactoring that will cause a circular reference
as it is.

Refactor sync APIs to reuse pagination API

Refactor get_recent_events_for_room return type

 Remove unused code path from member change DB func

 Refactor pagination DB API to return concrete type

The function is never called without a from_key, so we can remove all
the handling for that scenario.

 Refactor recent events func to use pagination func

The sync API often returns events in a topological rather than stream
ordering, e.g. when the user joined the room or on initial sync. When
this happens we can reuse existing pagination storage functions.

This allows calling the `get_recent_event_ids_for_room` function in more
situations.

nuke-room-from-db.sh: fix deletion from search table

There is no reason to return a tuple of tokens when the last token is
always the token passed as an argument. Changing it makes it consistent
with other storage APIs

This makes it easier to document what is being returned by the storage
functions and what some functions expect as arguments.

This also removes a cache that is unlikely to ever get hit.

Refactor /context to reuse pagination storage functions

nuke-room-from-db.sh: added postgresql option and help

notifications: Convert next_token to string according to the spec

Fix metrics that have integer value labels

Currently the parameter is serialized as an integer.

Signed-off-by: Konstantinos Sideris <sideris.konstantin@gmail.com>