Use senderTimestampMs instead of messageTimestamp

[allburov]

message.messageTimestamp contains timestamp in seconds, not in milliseconds as content.pollUpdateMessage.senderTimestampMs

It's important to get exact milliseconds for multi options poll, because we can get two message.update events with the same senderTimestampMs (because it's in seconds, not in milliseconds) so we can understand which vote is the latest one

Here's an event example:

{
    "messages.upsert": {
        "messages": [
            {
                "key": {...},
                "messageTimestamp": 1692774684,
                "message": {
                    "messageContextInfo": {...},
                    },
                    "pollUpdateMessage": {
                        "pollCreationMessageKey": {...},
                        "vote": {...},
                        "senderTimestampMs": "1692774684709"
                    }
                }
            }
        ],
        "type": "notify"
    },

There's .toNumber() because senderTimestampMs has Long type

{
  "low": 739148892,
  "high": 394,
  "unsigned": false
}

If we want to keep Long - let me know and I'll adjust the changes!

[whiskeysockets-bot]

Thanks for your contribution.

The next step is to wait for review and approval to merge it to main repository

The community can help reacting with a thumb up (:thumbsup:) for approval and rocket (:rocket:) for who has tested it.

To test this PR you can run the following command below:

# NPM
npm install @whiskeysockets/baileys@allburov/Baileys#fix-vote-timestamp
# YARN v2
yarn add @whiskeysockets/baileys@allburov/Baileys#fix-vote-timestamp

[allburov]

Let me know if I need to fix the "check-lint" type issues, I'll handle type it!

[PurpShell]

Looks good