feat: 🧑‍💻 Make Client.intents writable

[Paillat-dev]

Summary

I have no idea why intents were read-only in the first place. Maybe they should stay so, or maybe smth different should be done about it.

This PR allows to edit intents of a Client as long as the client wasn't connected yet.

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.

[BobDotCom]

I believe intents are read-only because they shouldn't be changed after initialization. Once the client connects, intents shouldn't change

[Paillat-dev]

I'm going to add some kind of check to see if the connection state is connected or not and act accordingly to allow or disallow the setting.

[Lulalaby]

I believe intents are read-only because they shouldn't be changed after initialization. Once the client connects, intents shouldn't change

Yeah that's the reason
If you'd find any way to change it after connect, discord would throw you out the connection

[Dorukyum]

The issue is something else entirely. This pull request adda a setter for intents attributes, the issue resides by the attributes of the discord.Intents class itself.

[Paillat-dev]

Yup I missed that. Let me rewrite all this a bit and come back

[Paillat-dev]

There we go