feat(GuildChannel): make createOverwrite and updateOverwrite not dependent on cache

[iShibi]

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

The above two methods need userOrRole to be in cache, so that they can be resolved in order to get the type of overwrite. This in some edge cases where the provided userOrRole is id of an uncached structure will throw an error. This PR adds a new optional parameter type for these two methods. Which can be used to manually set the type of the overwrite, making the methods not rely on the cache just to get the type.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• This PR changes the library's interface (methods or parameters added)
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[NotSugden]

typings need updating too

[ckohen]

I'd just like to point out that this fixes 2 of 8 methods that have this issue, most of the other ones take a role which is more likely to be cached, but there are still edge cases. I really like the way this was handled, not sure if this PR would be a good place to make changes to the other methods as well.

For reference, you can see these other methods in #5242

[kyranet]

Just one change to make CI pass

stale

stale

[vladfrangu]

This PR clashes with #5318 (if the mentioned PR gets merged first, this will need a full rebase)... @iCrawl how should we handle this?

[iCrawl]

Depends on what makes more sense to merge. Does a whole new manager really make sense here, except to abstract things more thoroughly?