Include the bot's permissions in interactions

[advaith1]

Description
Interactions already compute and provide the invoking member's (and provided members') permission values. However, it doesn't include the bot's permissions (if the application has a bot in the server).

Why This is Needed
Bots are expected to check permissions and not try to make requests that will 403. While this is easy in situations where all roles and channels are cached (usually through gateway events), this is not really possible to do in a stateless environment where you are only receiving interactions via HTTP and not receiving gateway events.

Alternatives Considered

• Technically could fetch the bot member, the channel, and the guild's roles whenever a command is used, but that's a lot of extra API requests
• Continuing to make requests without checking permissions; would lead to 403s though

[ckohen]

Additionally it would make sense to expand this to the resolved channels as well. Its all fine and gravy to check if a member has permission to do something in that channel, but it makes no difference if the bot can't do that too.

Making the request to check immediately can work in some circumstances, but in many it won't.

Example: logging channel

• User executes /config logging channel:<chanId>
• The bot can check the members permissions to access said channel (doesn't even really need to), but it also needs to check if it can send messages, maybe attach files too.
• We can check permissions by sending a "This channel has been set up for logging" or similar currently, but we don't always want to send a message at config time, so we only find out later when the user is no longer setting up the bot that we cannot send to that channel.

[ckohen]

• The original request has now been implemented with Add app_permissions #5131
• Would still really love to see the same for channel options