* Remove /users/@me call for socket and rework sharded client a bit

* Remove override for login

* Fix MessageUpdate when there's no channel cached

* Fix message events

* Fix cacheable type

* Fix examples

* Revert MessageUpdated

* Remove obsolete methods and properties

* Remove rest of GuildEmbed

* Remove TokenType.User

* Changes regarding the removal of the user tokentype

* Remove DM cache and fix references

* Move line back to where it was

* Create DM channel with id and author alone

* Unneeded cast

* First changes to the config

* Lots of changes to fit the new version

* Remove PermissionTargetConverter

This pull request adds the Discord Certified Moderator badge flag to the User Flags
PR in discord-api-docs: https://github.com/discord/discord-api-docs/pull/2946

Merged Discord.Net/dev into here

MESSAGE_REACTION_REMOVE_EMOJI events were triggering REST calls by invoking `RemoveAllReactionsForEmoteAsync` instead of `RemoveReactionsForEmote`, the latter being to handle cached message state cleanup.

* Scaffold Add/Remove roles by id. (needs impl & docs)

* Add docs

* Add implementation

* Expose Add/Remove role endpoints

* Formatting

* Fix wrong method call

When adding a type reader that replaces a default type reader,
CommandService checks that it replaces a type in its default type
readers or entity type readers (IMessage, IChannel, IRole, IUser). For
entity types, it checks that the target type is the same as the entity
type or it implements its type reader. Adding a type reader for a
default type reader doesn't make much sense and the original intent was
likely to check that the target type is or implements the entity type.

* Add guild member property for reaction

* Use the guild member provided by the event when present

```diff
--- geenrated
+++ generated
```

`Uri.IsWellFormedUriString()` doesn't return the expected result for specific urls, removed until the DotNet team actually resolves it ( https://github.com/dotnet/runtime/issues/21626 )