fix: dual-compat for WA Web 2.3000.1043xxx ($1 vs _serialized, downloadMedia)

[erickmourasilva]

Summary

• Add widSerialized() / normalizeSerialized() so WID/MsgKey work with both _serialized (legacy) and $1 (WA Web 2.3000.1043xxx+).
• Wire helpers into getMessageModel and getChatModel (fixes getChatById / typing crashes with r: r).
• Dual-read LID/PN in getContactLidAndPhone and Message _patch from/to/author.
• Use dual message id for downloadMedia / downloadMediaStream.
• In resolveMediaBlob, fall back to DownloadManager.downloadAndMaybeDecrypt when the in-memory blob is missing or looks thumbnail-sized vs msg.size.

Compatibility

• Old WA Web: unchanged path via _serialized.
• New WA Web: falls back to $1 and mirrors onto _serialized for node-side consumers.

Test plan

• Text receive + send on WA Web before 2.3000.1043xxx
• Text receive + send on WA Web 2.3000.1043xxx+
• msg.getChat() / typing indicator does not throw
• Incoming image: downloadMedia() returns full media (bytes ≈ msg.size, not thumbnail)
• getContactLidAndPhone still returns lid/pn strings

Closes #201831

Made with Cursor

[kulayRGB]

just heads up that _serialized to $1 rename is causing also msg.react() and msg.reply to fail silently. Adding react and reply fallback in Message.js fixes the issue. These fixes works for me

in async react(reaction)
-- from return this.client.sendReaction(this.id._serialized, reaction); --> to return this.client.sendReaction(this.id._serialized || this.id.$1, reaction);

in async reply()
-- from quotedMessageId: this.id._serialized, --> to quotedMessageId: this.id._serialized || this.id.$1