fix(InteractionCollector): handle thread (and parent) deletion

[kyranet]

Please describe the changes this PR makes and why it should be merged:

Backports the thread (and thread parent) channel deletion from #6902 to InteractionCollector with the fixed checks from #7069.

Fixes #6905

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

[Jiralite]

Fixes #6905

Another way to reproduce that issue is to create an interaction collector on a guild the client is not in, so this pull request doesn't actually fix this issue. Deleted channels are not sent to the client, so...

[kyranet]

For the code sample in the linked issue, you're using message.channel.createMessageComponentCollector, which will always set a guild the client is in, and of course, the collector will stop upon the guild's removal.

If you're somehow passing an invalid guild ID (or one that the bot isn't in), we can't determine it in any way due to Discord's limitations, and I believe that falls under user error.

Furthermore, the collectors have a timer specifically for things like this, if we can't determine a way to end a collector earlier, set a maximum timer so it won't leak.