feat(interactions): entry point commands

[shiftinv]

Summary

See discord/discord-api-docs@8bc883c.
Depends on #1571.

This implements the models/enums required to work with entry point application commands in the API, and adds InteractionResponse.launch_activity, which can be used with any non-ping/autocomplete interaction.

There isn't much of a point in attempting to integrate this into the existing command sync mechanisms more than the current state (i.e. simply keep existing entry point commands, unchanged) or into the ext.commands framework - these commands don't necessarily send an interaction to the app in the first place (see ApplicationCommandHandlerType.discord), and managing them through the bulk update endpoint isn't trivial (discord/discord-api-docs#7212).

Considering that all of this is only relevant to apps with embedded activities, it is already barely in scope for the library anyway. c:
Interactions triggered by this type of command can be handled through the application_command event listener just fine, in any case.

Checklist

• If code changes were made, then they have been tested
  • I have updated the documentation to reflect the changes
  • I have formatted the code properly by running uv run nox -s lint
  • I have type-checked the code by running uv run nox -s pyright
• 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, ...)

[read-the-docs-community]

Documentation build overview

📚 disnake | 🛠️ Build #33755556 | 📁 Comparing e1d611d against latest (16641e9)

  🔍 Preview build  

49 files changed · ± 49 modified

± Modified

• genindex.html
• index.html
• whats_new.html
• api/abc.html
• api/activities.html
• api/app_commands.html
• api/app_info.html
• api/audit_logs.html
• api/automod.html
• api/channels.html
• and 39 more...