Co-authored-by: Tommie Gannert <[email protected]>
Co-authored-by: Dan Peleg <[email protected]>

Co-authored-by: Neil Alexander <[email protected]>

The full event format is required for Sytest.

…faults.

Introduces "scope" as required by client API, and some small field
tweaks to make some 61push Sytests pass.

This manipulates account data over User API, and fires sync messages
for changes. Those sync messages should, according to an existing TODO
in clientapi, be moved to userapi.

Forks clientapi/producers/syncapi.go to pushserver/ for later extension.

A cleanup would be to move more of the name-splitting logic into
pushrules.go, to depollute routing.go.

This is the read-side. Pushserver will be the write-side.

…onsumer.

* Use one goroutine per user to avoid locking up the entire server for
  one bad push gateway.
* Split pushing by format.
* Send one device per push. Sytest does not support coalescing
  multiple devices into one push. Matches Synapse. Either we change
  Sytest, or remove the group-by-url-and-format logic.
* Write OutputNotificationData from push server. Sync API is already
  the consumer.

Supports m.read and m.fully_read receipts.

…c API with stream positions, instead of consuming directly