Enhancements to acknowledgment process, message sequence correction, and support for MediaOptions.Thumb

[eos175]

No description provided.

[AmarnathCJD]

properly tested ?
I can merge but dh have time to test :)

[eos175]

I am using this code in a couple of bots. Previously, messages like

Jul 19 11:06:11 neptuno turboPDFBot.app[355558]: 2024/07/19 11:06:11 gogram - mtproto - error - (retry: 1) [AUTH_KEY_INVALID] the auth key is invalid and needs to be reauthenticated (code -404)
Jul 19 11:06:11 neptuno turboPDFBot.app[355558]: 2024/07/19 11:06:11 gogram - mtproto - error - decoding unknown object: msg_seqno too high (similarly, there is a message with a higher msg_id but with either a lower or an equal and odd seqno) (code 33)
Jul 19 11:06:41 neptuno turboPDFBot.app[355558]: 2024/07/19 11:06:41 gogram - mtproto - error - (retry: 1) [AUTH_KEY_INVALID] the auth key is invalid and needs to be reauthenticated (code -404)
Jul 19 11:07:11 neptuno turboPDFBot.app[355558]: 2024/07/19 11:07:11 gogram - mtproto - error - decoding unknown object: msg_seqno too low (the server has already received a message with a lower msg_id but with either a higher or an equal and odd seqno) (code 32)
Jul 19 11:07:41 neptuno turboPDFBot.app[355558]: 2024/07/19 11:07:41 gogram - mtproto - error - (retry: 1) [AUTH_KEY_INVALID] the auth key is invalid and needs to be reauthenticated (code -404)

would appear, and the seqNo were not being generated according to Telegram's specifications. For now, those messages have not reappeared, and everything seems to be working fine. However, more testing may still be needed.