Migrate the message poll to the generated PollResponseData model - #6680

Goal

Parse the poll embedded in a message with the generated PollResponseData.

Part of AND-1291

Implementation

• Point DownstreamMessageDto.poll at PollResponseData, the model the poll endpoints already use, and follow the field rename in lastUpdateTime(). PollResponseData.toDomain() was already in place, so no mapping code is added.
• Enrich the nested vote, answer and creator users in the message fixture. The generated UserResponse requires created_at, updated_at and language, and the fixture carried only id, role, banned and online.

DownstreamPollDto stays for the poll events, which still parse it.

Notes

The message carries Poll *commonpayloads.PollResponseData, the same struct the poll endpoints return, and created_at, updated_at and language are non-omitempty on UserResponseCommonFields. So the wire always sends them for a nested poll user and the old fixture was the unrealistic part.

The two paths swap strictness on three keys. voting_visibility was String? and defaulted to PUBLIC; it is required on PollResponseData, so a poll that omits it now throws on the DTO path while PollAdapter still defaults it. options and own_votes go the other way, defaulting to empty on the DTO path while PollAdapter still throws. None can fire in practice: all three are plain non-omitempty tags on the Go response struct.

A custom key with a null value no longer reaches Poll.extraData. The DTO path used to keep it and the direct path already dropped it, so this aligns them.

Testing

• Device probe: created a poll with custom data on the poll and on one option, sent it, cast a vote and an answer, then read the message back through getMessage and queryChannels. Both custom values round-tripped, config was preserved, and every nested user (creator, votes, own votes, answers) carried the three required fields.
• Mutation checks: nulling message.poll, and dropping poll.updatedAt from lastUpdateTime, each fail 6 tests.
• MessageParsingTest gains a case for poll and option custom data inlined on the message, which also pins the null-valued key being dropped on both paths.

Summary by CodeRabbit

• Bug Fixes
  • Poll messages now correctly reflect the poll’s latest update time.
  • Poll data is mapped consistently, preserving custom poll information in message details.
  • Poll-related user information, including creator, voters, and respondents, is handled more completely.
• Tests
  • Expanded coverage for poll custom data, optional message properties, timestamps, and user metadata.