feat: Add ComponentLimits and EmbedLimits classes for constraint defini…

[Lumabots]

Summary

Information

• This PR fixes an issue.
• This PR adds something new (e.g. new method or parameters).
• This PR is a breaking change (e.g. methods or parameters removed/renamed).
• This PR is not a code change (e.g. documentation, README, typehinting,
  examples, ...).

Checklist

• I have searched the open pull requests for duplicates.
• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
• If type: ignore comments were used, a comment is also left explaining why.
• I have updated the changelog to include these changes.
• AI Usage has been disclosed.
  • If AI has been used, I understand fully what the code does
• I have read the Contributing Guidelines

[pycord-app]

Thanks for opening this pull request!
Please make sure you have read the Contributing Guidelines and Code of Conduct.

This pull request can be checked-out with:

git fetch origin pull/3217/head:pr-3217
git checkout pr-3217

This pull request can be installed with:

pip install git+https://github.com/Pycord-Development/pycord@refs/pull/3217/head

[Paillat-dev]

Not sure, do we actually want these ? Seems like a pain to maintain. Or was this discussed already and I missed it ?

[Soheab]

I don't mind this, but can we at least use it in the library? We hardcode all the limits currently, and just having these enums without doing anything with them does seem unnecessary.

Also, maybe we shouldn't document the limits in the docs? It's easier to change the enum values when needed, and users can read it/use it from there. I think it's unlikely that users will first see it in the docs.

[Lumabots]

well inside py-cord we dont even check for limit, so its not even hardcoded (except in the docs but i dont think we can change that)
for embed, for component it will be useful and i will make the change

[Soheab]

well inside py-cord we dont even check for limit, so its not even hardcoded (except in the docs but i dont think we can change that)

for embed, for component it will be useful and i will make the change

Oh yeah, not for embeds… we could do that..

[Lumabots]

i put that now for the next commit, i dont know so much what to put for min values for file as

min_values?* | integer | Minimum number of items that must be uploaded (defaults to 1); min 0 (see note), max 10
* min_values must be either omitted or at least 1 if required is omitted or true.

[Lumabots]

for row, i didnt edit it as its not very clear to me, we did put row should be betwee, 5 and 1, but isnt that only for View and not designer view ? but row property in select doesnt make any difference betwee, those 2

[Lumabots]

my first reason to use enum instead of class is that they are non breaking, but i'll edit them as class