refactor(ThreadMemberManager): #remove accepts UserResolvable

[Renegade334]

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

Adds the ability to pass a resolvable to ThreadMemberManager#remove, in keeping with other manager functions.

Note that this deliberately accepts a UserResolvable to pass to UserManager#resolveId, rather than a ThreadMemberResolvable to pass to ThreadMemberManager#resolveId. There are two reasons for this:

• UserManager#resolveId accepts a ThreadMember as an argument anyway;
• If the client lacks the privileged GUILD_MEMBERS intent, then the ThreadMemberManager cache is never populated, so ThreadMemberManager#resolveId always returns null. (ref)

The new argument type is a superset of the old one, and so this is suitable for semver:patch.

Discussion:

• Both ThreadMemberManager#add and #remove accept a reason argument, but neither API endpoint supports the X-Audit-Log-Reason header, as neither event is loggable. I've left them there, as removing the arguments would technically be a breaking change, but these should probably be removed at some point.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
discord-js	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 1, 2023 0:34am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
discord-js-guide	⬜️ Ignored (Inspect)	Visit Preview		Dec 1, 2023 0:34am