Fix incorrect and inconsistent timeout types

[revolter]

No description provided.

[Bibo-Joshi]

Hi. I'm not quite sure what this PR is aiming at. Would you mind explaining where you see inconsistency in the types? IISC we use float everywhere.

[revolter]

Yes, sure, sorry for not explaining it from the start.

So, knowing that the official getUpdates API declares timeout as Integer, here are some of the inconsistencies:

1. The Updater.start_polling correctly declares it as int:

   python-telegram-bot/telegram/ext/_updater.py

   Line 187 in 57c780c

   timeout: int = 10,

   but it's incorrectly documented as float:

   python-telegram-bot/telegram/ext/_updater.py

   Line 205 in 57c780c

   timeout (:obj:`float`, optional): Passed to

2. The Bot.get_updates incorrectly declares it as float:

   python-telegram-bot/telegram/_bot.py

   Line 3589 in 57c780c

   timeout: Optional[float] = None,

   although it's correctly documented as int:

   python-telegram-bot/telegram/_bot.py

   Line 3624 in 57c780c

   timeout (:obj:`int`, optional): Timeout in seconds for long polling. Defaults to ``0``,

So, the bottom line is that all of them should be int, which is what this PR does.

[revolter]

Let me know if you agree, and I'll rebase and fix the conflicts 👍🏻

[Bibo-Joshi]

Thanks for the explanation and the catch! Yes, I would like to have the merged, then :) Would you mind resolving the merge conflicts?

[revolter]

All done 😁

[Bibo-Joshi]

Than you for the contribution!

[revolter]

And thank you for merging!