feat: Components v2

[silasary]

Pull Request Type

• Feature addition
• Bugfix
• Documentation update
• Code refactor
• Tests improvement
• CI/CD pipeline enhancement
• Other: [Replace with a description]

Description

Support for Components v2.
It's probably not perfect, but it works and I'm happy enough to ship it.

Changes

Related Issues

Test Scenarios

Python Compatibility

• I've ensured my code works on Python 3.10.x
• I've ensured my code works on Python 3.11.x

Checklist

• I've run the pre-commit code linter over all edited files
• I've tested my changes on supported Python versions
• I've added tests for my code, if applicable
• I've updated / added documentation, where applicable

[AstreaTSS]

Before we merge this, I do want to say that we need to expose all of the new classes through the various __init.py__s.

[fin-github]

Just got the error:

POST::https://discord.com/api/v10/interactions/1368954513607753829/aW50ZXJhY3Rpb246MTM2ODk1NDUxMzYwNzc1MzgyOTpHMWhPdXFCcXlQODV3d1Z5VEZ3eXJjYlNBZmJrS0pDSmdmYXkzZ3hqNHc0bmF2MVJFaVVNZGRDUmpHc2JlQXVSSXBkQ2FxSzlyTXg0bmlyaUx4dzhOd2NUT2o4RkxEbjJWMlVvQlNwRFRHdWNkMWRwdGhtSDNacFJJOUc3T2lXdQ/callback: 400
Ignoring exception in cmd `/v2`: HTTPException: 400|Bad Request: data->components->0 UNION_TYPE_CHOICES: Value of field "type" must be one of (1, 9, 10, 12, 13, 14, 17).

I have fixed it, but heres the result it sends if you want to make a more descriptive error for when this occurs.

Whenever you use a V1 component with a V2 component, it causes this error.