Check-list for PRs

• Added .. versionadded:: NEXT.VERSION, .. versionchanged:: NEXT.VERSION, .. deprecated:: NEXT.VERSION or ``.. versionremoved:: NEXT.VERSION` to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)
• Created new or adapted existing unit tests
• Documented code changes according to the CSI standard
• Added myself alphabetically to AUTHORS.rst (optional)
• Added new classes & modules to the docs and all suitable __all__ s
• Checked the Stability Policy in case of deprecations or changes to documented behavior

If the PR contains API changes (otherwise, you can ignore this passage)

• Checked the Bot API specific sections of the Stability Policy

• Created a PR to remove functionality deprecated in the previous Bot API release (see here)

• New Classes

  • Added self._id_attrs and corresponding documentation
  • __init__ accepts api_kwargs as keyword-only

• Added New Shortcuts

  • In telegram.Chat & telegram.User for all methods that accept chat/user_id
  • In telegram.Message for all methods that accept chat_id and message_id
  • For new telegram.Message shortcuts: Added quote argument if methods accept reply_to_message_id
  • In telegram.CallbackQuery for all methods that accept either chat_id and message_id or inline_message_id

• If Relevant

  • Added new constants at telegram.constants and shortcuts to them as class variables
  • Linked new and existing constants in docstrings instead of hard-coded numbers and strings
  • Added new message types to telegram.Message.effective_attachment
  • Added new handlers for new update types
    • Added the handlers to the warning loop in the telegram.ext.ConversationHandler
  • Added new filters for new message (sub)types
  • Added or updated documentation for the changed class(es) and/or method(s)
  • Added the new method(s) to _extbot.py
  • Added or updated bot_methods.rst
  • Updated the Bot API version number in all places: README.rst (including the badge) and telegram.constants.BOT_API_VERSION_INFO

Topics in private chats

• Added the field has_topics_enabled to the class User, which can be used to determine whether forum topic mode is enabled for the bot in private chats.
• Added the method sendMessageDraft, allowing partial messages to be streamed to a user while being generated.
• Added the field is_name_implicit to the classes ForumTopic and ForumTopicCreated.
• Supported the fields message_thread_id and is_topic_message in the class Message for messages in private chats with forum topic mode enabled.
• Supported the parameter message_thread_id in private chats with topics in the methods sendMessage, sendPhoto, sendVideo, sendAnimation, sendAudio, sendDocument, sendPaidMedia, sendSticker, sendVideoNote, sendVoice, sendLocation, sendVenue, sendContact, sendPoll, sendDice, sendInvoice, sendGame, sendMediaGroup, copyMessage, copyMessages, forwardMessage, and forwardMessages, allowing bots to send a message to a specific topic.
• Supported the parameter message_thread_id in private chats in the method sendChatAction, allowing bots to send chat actions to a specific topic in private chats.
• Supported the parameter message_thread_id in private chats with topics in the method editForumTopic, deleteForumTopic, and unpinAllForumTopicMessages, allowing bots to manage topics in private chats.

For now testing the new method send_message_draft is done without request. To test them effectively (with request) we'll have to manually create a topic in one of the test bots as unlike supergroup topics they can not be created programmatic ally.

The name for the new Message shortcut Message.reply_text_draft can be discussed. I also debated having reply_{markdown[v2],html}_draft or not. markdown would make sense i guess as llms often output in markdown but then we should have all of them for consistency with reply_{text,..} (?)

ps
should be ready for review i just need to give it one myself before requesting to make sure its up to date with latest TG release.