refactor: Use Event instead of EventUpdate for storing in db

[krille-chan]

Fixes https://github.com/famedly/product-management/issues/1875

[coder-with-a-bushido]

should we have an onInviteStateEvent stream too? It's the only case where the event is not MatrixEvent but a StrippedStateEvent

[krille-chan]

No because this would be a duplication of onSync where you can just filter. This is for events after potential decryption

[coder-with-a-bushido]

Ok, but we use onEvent for local notifications. If there's no onInviteStateEvent then we would miss inviteState updates to show local notifications.

[coder-with-a-bushido]

Suggested change

	redactedEvent.setRedactionEvent(redactionEvent);
	redactedEvent.setRedactionEvent(event);

[coder-with-a-bushido]

Just confirming. We removed it because it's already handled below right?

    // Store a common state event
    if (stateKey != null &&
        // Don't store events as state updates when paginating backwards.
        (eventUpdate.type == EventUpdateType.timeline ||
            eventUpdate.type == EventUpdateType.state ||
            eventUpdate.type == EventUpdateType.inviteState)) {
      if (eventUpdate.content['type'] == EventTypes.RoomMember) {
        await _roomMembersBox.put(
          TupleKey(
            eventUpdate.roomID,
            eventUpdate.content['state_key'],
          ).toString(),
          eventUpdate.content,
        );
      } else {
        final type = eventUpdate.content['type'] as String;
        final roomStateBox = client.importantStateEvents.contains(type)
            ? _preloadRoomStateBox
            : _nonPreloadRoomStateBox;
        final key = TupleKey(
          eventUpdate.roomID,
          type,
          stateKey,
        ).toString();

        await roomStateBox.put(key, eventUpdate.content);
      }
    }

[coder-with-a-bushido]

Suggested change

	(type == EventUpdateType.timeline ||
	type == EventUpdateType.state ||
	type == EventUpdateType.inviteState)) {
	{EventUpdateType.timeline, EventUpdateType.state, EventUpdateType.inviteState}.contains(type)) {

[coder-with-a-bushido]

I think there's enough usage of event.unsigned?.tryGet<String>('transaction_id') to create a getter txid in the Event class. Should we create one? I can open a separate PR for that if you agree.

[coder-with-a-bushido]

I think we could also have a event.type check here for all these 3 cases (just like before)