In future version events won't have an event ID, so we won't be able to
do this check.

We only process events sent to us from a server if the event ID matches
the server, to help guard against federation storms. We replace this
with a check against the event origin.

The transaction queue only sends out events that we generate. This was
done by checking domain of event ID, but that can no longer be used.
Instead, we may as well use the sender field.

The event ID is changing, so we can no longer get the domain from it. On
the other hand, the check is unnecessary.

Since newer versions of events don't have the same format for event ID.

Refactor event building into EventBuilder

Fixup calls to `comput_event_signature`

I got fed up with always adding '@unittest.DEBUG' every time I needed to debug a test.

We currently pass FrozenEvent instead of `dict` to
`compute_event_signature`, which works by accident due to `dict(event)`
producing the correct result.

This fixes PR #4493 commit 855a1510

Implement fallback for V2 invite API

`.user_id` is proxed to `.sender` in FrozenEvent, so this has no
functional change

This is so that everything is done in one place, making it easier to
change the event format based on room version

Split up event validation between event and builder

This bug was introduced in PR #4470, commit 678a92cb

* fix obvious problem :|

* changelog

Refactor event signing to work on dicts

two reasons for this. One, it saves a bunch of boilerplate. Two, it squashes
unicode to IDNA-in-a-`str` (even on python 3) in a way that it turns out we
rely on to give consistent behaviour between python 2 and 3.

Pass through room version to event auth

If the room version is either 1 or 2 then a server should retry failed
`/v2/invite` requests with the v1 API

* load cert

* changelog

* fix

The validator was being run on the EventBuilder objects, and so the
validator only checked a subset of fields. With the upcoming
EventBuilder refactor even fewer fields will be there to validate.

To get around this we split the validation into those that can be run
against an EventBuilder and those run against a fully fledged event.