Goal

Parse the user carried by the user, read and delivery events with the generated models the backend
serializes them from.

Part of AND-1291

Implementation

• Point user on user.updated at UserResponsePrivacyFields, and on user.presence.changed,
  user.deleted, user.watching.start/stop, the channel and global ban/unban events,
  message.delivered, notification.mark_read (per channel and mark-all), notification.mark_unread and
  user.messages.deleted at UserResponseCommonFields. These match the structs the backend embeds in each
  event. Vendors both models.
• Add their mappers to User, and collecting adapters so the flattened custom fields land in custom.
• Keep deleted_at and revoke_tokens_issued_before in extraData as well. Both models declare them and
  the domain has no property for either.
• Read devices out of the custom data into the typed devices, and drop it from extraData.

Notes

Neither model declares devices, but event users can carry a device list as custom data, in the request
shape. The previous DTO declared the key, so it always ended up in User.devices. Without promoting it, it
would surface in extraData and, because user.updated merges into the current user, in the current user's
extraData too.

language goes from nullable to required. It is a plain non-pointer tag on the shared user fields, so it is
always sent. The event test fixtures now use the shapes these events actually carry, without the own-user
state (devices, mutes, unread counts) the previous shared fixture had.

On the read and delivery events the backend embeds the user as optional (json:"user,omitempty"), while
the DTOs keep it required. In practice the reader is always set: the mark-all-read constructor dereferences
it directly. Keeping it required matches the previous behavior.

The mock server does not emit the user events; it builds notification.mark_unread from a recorded user
that has every required field.

Testing

Mutation sweep over both mappers: zero survivors. A parsing test feeds whole event payloads through the
parser to cover the adapters, the kept keys and the devices promotion end to end.

Device-probed user.updated, user.watching.start, notification.mark_unread, notification.mark_read and
mark-all-read with a custom field set on the user: language, the custom field and 16 devices came through
the typed fields, with no devices key in the event user's or the current user's extraData. Presence, ban,
delete, message.delivered and user.messages.deleted are not reachable from a single client and are
covered by the parsing tests.

Summary by CodeRabbit

• Bug Fixes
  • User information in chat events is now mapped more accurately, including privacy settings and device details.
  • Additional user data, such as deletion and token-revocation details, remains available in event data.