contrib.telegram: gracefully handle creation rate limit

[casperdcl]

• fixes Telegram "Too Many Requests" Error #1220
• fixes tqdm_telegram exhausts message quota because of frequent updates #1076
• replaces/closes Avoid telegram limit hit #1221

[codecov]

Codecov Report

Merging #1223 (e02e77a) into devel (0b64cfe) will increase coverage by 0.29%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            devel    #1223      +/-   ##
==========================================
+ Coverage   89.59%   89.88%   +0.29%     
==========================================
  Files          26       26              
  Lines        1721     1721              
  Branches      286      286              
==========================================
+ Hits         1542     1547       +5     
+ Misses        132      128       -4     
+ Partials       47       46       -1     

[Hagai]

I love the improvements in this merge, I suggested robustness and readability improvements.

[Hagai]

Since this result came from external API I would assert 'result' and 'message_id' exists before accessing them.
Example for a possible error: authentication failure.

[Hagai]

I guess you intended to initialize '_message_id' property using this line, while it works, I think it can be clearer.
I would suggest a minor modification to avoid Codacy flag this as "Statement seems to have no effect" and "Access to member '_message_id' before its definition line 56".
Here define "self._message_id = None" and later instead of "hasattr(self, '_message_id')" use "self._message_id is None".
I would also put lines 44 to 56 in separate method (named initialize_message_id or a similar name). And I would explicitly call it to make the intension clearer (instead of accessing the message_id preperty).
message_id property will also call this method if self._message_id is None