Fixing Client connection error

[sander76]

Description:

During long polling, when a "Client connect error" occurred (for example by an async timeout) the return value seemed to block the flow unable to recover and completely disable the telegram_bot.

This fix should let the "Client connect error" occur, but allow for recovery of the bot.

Related issue (if applicable): fixes #
#7328
#7938

Checklist:

If the code communicates with devices, web services, or third-party tools:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• Tests have been added to verify that the new code works.

[mention-bot]

@sander76, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff, @azogue and @pvizeli to be potential reviewers.

[balloob]

Thanks