Thiscloses#3004.

Checklist for PRs

• Added.. versionadded:: version,.. versionchanged:: version or.. deprecated:: 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 theCSI standard
• Added myself alphabetically toAUTHORS.rst (optional)
• Added new classes & modules to the docs and all suitable__all__ s

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

• New classes:

  • Addedself._id_attrs and corresponding documentation
  • __init__ accepts**_kwargs

• Added new shortcuts:

  • InChat &User for all methods that acceptchat/user_id
  • InMessage for all methods that acceptchat_id andmessage_id
  • For newMessage shortcuts: Addedquote argument if methods acceptsreply_to_message_id
  • InCallbackQuery for all methods that accept eitherchat_id andmessage_id orinline_message_id

• If relevant:

  • Added new constants attelegram.constants and shortcuts to them as class variables
  • Link new and existing constants in docstrings instead of hard coded number and strings
  • Add new message types toMessage.effective_attachment
  • Added new handlers for new update types
    • Add the handlers to the warning loop in theConversationHandler
  • Added new filters for new message (sub)types
  • Added or updated documentation for the changed class(es) and/or method(s)
  • Added or updatedbot_methods.rst
  • Updated the Bot API version number in all places:README.rst andREADME_RAW.rst (including the badge), as well astelegram.constants.BOT_API_VERSION
  • Added logic for arbitrary callback data intg.ext.Bot for new methods that either accept areply_markup in some form or have a return type that is/containstelegram.Message