Expose Member interface

[felldo]

What feature are you proposing?

This should serve as the current working state and what still needs to be done in the development of exposing the Member interface.

• SlashCommandInteractionOption needs to have methods to expose the member option in addition to user option (they are the same command option type but differently resolved)
• Check for all CompletableFuture<User>, Optional<User> and normal User return types if it needs to be converted to returning a member or additional methods need to be added to get a Member
• Rework listener names (verify if ServerMember*Listener are appropriate) and structure to match the correct things they dispatch from (Member/User). Currently the structure of OptionalUserEvent does not properly fit for events like UserStartTypingEvent which get a Member object if it's from a Server
• Decide whether the Member should extend from the User and depending on that, listeners need to be reworked a bit to make them attachable to Members / Users

[RealYusufIsmail]

Will have a look at the slash command option one

[Saladoc]

I think all of those issues are addressed in the linked PR which I did not have time to review yet due to the scope. @KILLEliteMaste can you clarify?

[felldo]

The linked PR is the minimum that is required to expose the Member interface. The development has been moved to the Javacord refactor/expose-member branch. All bullet points above have been added after the PR has been made so they are all still open / left to do. PRs to address these or new issues should be made against the refactor/expose-member Javacord branch