Remove unnecessary instance check in autocomplete

[DefiDebauchery]

Summary

Fixes #1630

The autocomplete hooks recently had typechecking applied, which would only pass if a command was specifically a Command. Currently, sub-commands are an instance of SlashCommandGroup. Because of this, the check would fail, and autocomplete Options in subcommands would fail to execute.

Note that ApplicationCommand also encompasses Bridged commands and Context (Message/User) commands. I'm happy to update this PR to change typechecking for (Command, SlashCommandGroup) if needed, but this is better than having subcommand autocomplete being broken.

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.

[Dorukyum]

Maybe we should instead prevent SlashCommandGroups from being passed here

[Lulalaby]

Maybe we should instead prevent SlashCommandGroups from being passed here

Would be another good approach
@DefiDebauchery what you think

[DefiDebauchery]

I suppose that depends on whether subcommands are intended to be SlashCommandGroups as they currently are. IIRC there's some limitation about being able to pull subcommands out into a unique Command (but I could be way off here)

But the issue is that autocomplete in subcommands are completely broken in the currently-published version of Pycord. This PR essentially just reverts the typecheck change that happened in this release.

Because of that, I feel that fixing this aspect should take precedence, while the larger-scope task of correcting types is ongoing (assuming it does require some dedicated work).

[Dorukyum]

Subcommands are SlashCommand objects, they are just stored in SlashCommandGroup.subcommands

I think, while we're at it, we should fix the issue from the root

[DefiDebauchery]

Of course. No argument about fixing issues at a fundamental level.

However, I don't think other users of subcommands should be left out of a working version while that takes place. It's currently broken in production.

[Lulalaby]

@Dorukyum please lets merge this as temporary fix
@BobDotCom please make a rc of that