feat: right-clickybois (context menu support for ApplicationCommand and CommandInteraction)

[monbrey]

This adds support for creating Application Commands in right-click context menus, and receiving the interactions.

The received data is parsed into the CommandOptionResolver as seamlessly as possible:

• A command acting on a user creates a USER type option: getUser('user) / getMember('user')
• A command acting on a message creates a fake _MESSAGE type option for the new getMessage('message')

The type of application command is yet to be included in the interaction data, but when it is this will be updated to use that rather than relying on the existence of target_id.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)

[ThaTiemsz]

ApplicationCommand is missing a type property.

[advaith1]

imo it's a bad idea to stick the target information into options; currently context cmds can't have options but they might add support in the future, and also it's not really good ux to just make fake options. it would be better to have dedicated target properties; maybe interaction.target.id, interaction.target.message, interaction.target.user, and interaction.target.member?

[monbrey]

Friendly reminder that draft PR means not ready for review

[iCrawl]

This needs a rebase.

[SpaceEEC]

One small doc nit, otherwise LGTM

Stale

[ThaTiemsz]

ApplicationCommand#type should be added so that it's possible to check whether the command is a slash command or context menu.

[monbrey]

That's only on Interaction though. You can't do that with commands that are cached that you've fetched from the API.

Right, I misread. Will do.

Stale

[ThaTiemsz]

You forgot to update the ApplicationCommand types, otherwise LGTM!

[iCrawl]

This needs a rebase.