Closes parts of#4459

• Added the ability to specify a payload insendPaidMedia that is received back by the bot inTransactionPartnerUser and purchased_paid_media updates. (Taken by@aelkheir)
• Added the field prize_star_count to the classesGiveawayCreated,Giveaway,GiveawayWinners andChatBoostSourceGiveaway. (Taken by@aelkheir)
• Added the field is_star_giveaway to the classGiveawayCompleted. (Taken by@aelkheir)

Checklist 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 theCSI standard <https://standards.mousepawmedia.com/en/stable/csi.html>__
• Added myself alphabetically toAUTHORS.rst (optional)
• Checked theStability Policy <https://docs.python-telegram-bot.org/stability_policy.html>_ 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 theStability Policy <https://docs.python-telegram-bot.org/stability_policy.html>_
• Created a PR to remove functionality deprecated in the previous Bot API release (see here <https://docs.python-telegram-bot.org/en/stable/stability_policy.html#case-2>_)
• New classes:
  • Addedself._id_attrs and corresponding documentation
  • __init__ acceptsapi_kwargs as kw-only
• Added new shortcuts:
  • In :class:~telegram.Chat & :class:~telegram.User for all methods that acceptchat/user_id
• If relevant:
  • Link new and existing constants in docstrings instead of hard-coded numbers and strings
  • Added or updated documentation for the changed class(es) and/or method(s)