Don't redact create events

These events don't contain anything that could jeopardize voters' ballots

Upgrade mautrix-go from v0.10.11 to v0.12.1

Configure gnark logger to use logs file

and fail if log file can't be opened

Upgrade gnark from v0.6.4 to v0.7.1

https://github.com/ConsenSys/gnark/blob/v0.7.1/CHANGELOG.md

Upgrade gnark from v0.5.2 to v0.6.4

gnark v0.6.0 contains many breaking changes
https://github.com/ConsenSys/gnark/blob/master/CHANGELOG.md#v060---2022-01-03

The tallyard version is also bumped to v0.5.0 since the SeedPart param in the
JoinElection message (xyz.tallyard.join) has been dropped.

Bump version to v0.4.5

Ensure elections have more than voter

because having one voter doesn't make any sense, and causes panics in the
cryptography code.

Some refactoring is also done in ElectionWaitTUI to improve readability.

Ensure we process the start message before processing evals

This is why we've sometimes seen panics when FinalJoinIDs is nil

Check for nil pointer

We've been seeing nil pointer panics in this function.

Bump version to v0.4.4

Lazy load member state events

https://matrix.org/docs/spec/client_server/r0.6.0#lazy-loading-room-members

README: better wording

contrib: add _incr_version script

See https://drewdevault.com/2019/10/12/how-to-fuck-up-releases.html

Bump version to v0.4.3

Close files used in marshalling

Bump version to v0.4.2

Print helpful error message when the map schema is incompatible

Speed up marshalling by storing keys in separate files

Won't do TODO

It's basically not possible to have "no limit" (and this is actually a good
thing).

Correctly include state events in sync timeline

I thought all states were exclusively returned via the state list.

See "Rationale" under https://spec.matrix.org/v1.2/client-server-api/#syncing