Add functions that set permissions for all slash commands in a cog

[EmmmaTech]

Summary

This pull request implements #495 by having new functions that loop through each command and set the permissions

Checklist

• 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
• 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, ...)

[Dorukyum]

Not a bad idea but it would be inconsistent since ext.commands.Cog uses the cog_check async method.

[EmmmaTech]

Not a bad idea but it would be inconsistent since ext.commands.Cog uses the cog_check async method.

So should I rework the PR around that?

[EmmmaTech]

Thinking about it, the way I worded the title gives the wrong impression because none of the functions I added are actually decorators. So I guess I should just change the title of the PR

[EmmmaTech]

Wait how did that dismiss the reviews

[Dorukyum]

By the way, how are these meant to be used?

[EmmmaTech]

By the way, how are these meant to be used?

I intended for the functions to be used in cog_check, however I added 0 checks for that, so it could be used in the init function or any other function in the cog.

[Dorukyum]

By the way, how are these meant to be used?

I intended for the functions to be used in cog_check, however I added 0 checks for that, so it could be used in the init function or any other function in the cog.

How can these be used in the cog_check? That is a method ran as a check before every command of the cog while these methods set permissions for the commands.
Cog decorators could be used for this functionality instead.

[EmmmaTech]

By the way, how are these meant to be used?

I intended for the functions to be used in cog_check, however I added 0 checks for that, so it could be used in the init function or any other function in the cog.

How can these be used in the cog_check? That is a method ran as a check before every command of the cog while these methods set permissions for the commands.
Cog decorators could be used for this functionality instead.

Okay, but do you know which function these cog decorators would go in?

Plus, I have a better idea: each of the functions could still be ran in cog_check, however, it would just store an array of the permissions in the cog. Then later on, in another function, each of these permissions are loaded into every function.

[Lulalaby]

⚠️ Warning: This is a candidate for getting closed
ℹ️ Reason: Collides with perms 2.1

[EmmmaTech]

⚠️ Warning: This is a candidate for getting closed

ℹ️ Reason: Collides with perms 2.1

Could I redesign it around the perms in 2.1?

[Lulalaby]

No

[EmmmaTech]

No

Okay. You can close it then if you'd like

[Lulalaby]

We discuss it internally

[EmmmaTech]

Closing because of reworks with Command Permissions.