Add missing enums, check existing ones, drop helpers

[evgfilim1]

Enums in the API

• ChatType: Type of chat, can be either “private”, “group”, “supergroup” or “channel”
• MessageEntityType: Type of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD), “bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” (do-not-reply@telegram.org), “phone_number” (+1-212-555-0123), “bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “spoiler” (spoiler message), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs), “text_mention” (for users without usernames)
• DiceEmoji: Currently, must be one of “🎲”, “🎯”, “🏀”, “⚽”, “🎳”, or “🎰”.
• PollType: Poll type, currently can be “regular” or “quiz”
• ChatMemberStatus
• BotCommandScopeType
• MenuButtonType
• InputMediaType
• ParseMode: MarkdownV2, Markdown, HTML
• ChatAction (Add class helper ChatAction #803): Type of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, choose_sticker for stickers, find_location for location data, record_video_note or upload_video_note for video notes.
• MaskPositionPoint: The part of the face relative to which the mask should be placed. One of “forehead”, “eyes”, “mouth”, or “chin”.
• InlineQueryChatType (merge with ChatType?): Optional. Type of the chat from which the inline query was sent. Can be either “sender” for a private chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
• InlineQueryResultType
• EncryptedPassportElementType (move to PassportElementType?): Element type. One of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”, “phone_number”, “email”.
• PassportElementErrorSource
• PassportElementErrorDataFieldType (so long :/, merge to PassportElementType?): The section of the user's Telegram Passport which has the error, one of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”
• PassportElementErrorFrontSideType (same): The section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
• PassportElementErrorReverseSideType (same): The section of the user's Telegram Passport which has the issue, one of “driver_license”, “identity_card”
• ...ErrorSelfieType (same): The section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
• ...ErrorFileType (same): The section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
• ...ErrorFilesType (huh?, same): The section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
• ...ErrorTranslationFileType (same): Type of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
• ...ErrorTranslationFilesType (same): Type of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”

Custom enums

• ContentType: Message fields
• UpdateType (maybe): Update fields

[JrooTJunior]

This issue now is pinned on top of all issues, as the main priority for Beta 6 is aliases/shortcuts for methods in types.

In general, it is planned to re-implement code generation based on declarative configuration for types, methods, shortcuts.

The second goal is an auto-generation of Enums for common set of values (like chat type, dice emojies and etc.).

[evgfilim1]

Related: aiogram/tg-codegen#11