refactor(GuildMember): remove GuildMember#hasPermission

[Extroonie]

Please describe the changes this PR makes and why it should be merged:
Similar to all other removals for v13. GuildMember#hasPermission is functionally same as GuildMember#permissions#has. Unlike the only addition checkOwner for this entire method, that the users can very easily implement.

Status

• 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

Semantic versioning classification:

• This PR changes the library's interface (methods or parameters added)
  • This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• This PR only includes non-code changes, like changes to documentation, README, etc.

[Mesteery]

Why not deprecating it before removing it ?

[kyranet]

Why not deprecating it before removing it ?

Deprecating makes sense only when something is removed as soonest as the next major.

Unfortunately, the v12 line is unmaintained, and we're doing changes to v13, it wouldn't make any sense to deprecate a method and then remove it in the following commit.