feat: Application Emojis

[Lulalaby]

Description

This implements Application Emojis (THANKS MAISY).
Breaking change in DiscordEmoji.TryFromName (additional required parameter)

Added methods, properties & objects

• BaseDiscordClient.Emojis- (IReadOnlyDictionary<ulong, DiscordApplicationEmoji>)
• DiscordClient.Emojis- (IReadOnlyDictionary<ulong, DiscordApplicationEmoji>)
• DiscordClient.GetApplicationEmojisAsync(bool fetch = false) - (Task<IReadOnlyList<DiscordApplicationEmoji>>)
• DiscordClient.GetApplicationEmojiAsync(ulong id, bool fetch = false) - (Task<DiscordApplicationEmoji?>)
• DiscordClient.CreateApplicationEmojiAsync(string name, Stream image) - (Task<DiscordApplicationEmoji>)
• DiscordClient.ModifyApplicationEmojiAsync(ulong id, string name) - (Task<DiscordApplicationEmoji>)
• DiscordClient.DeleteApplicationEmojiAsync(ulong id)
• DiscordConfiguration.AutoFetchApplicationEmojis
• DiscordApplicationEmoji
• DiscordApplicationEmoji.ModifyAsync(string name) - (Task<DiscordApplicationEmoji>)
• DiscordApplicationEmoji.DeleteAsync()
• DiscordEmoji.FromApplicationEmote(BaseDiscordClient client, ulong id)- (DiscordEmoji), can be casted to DiscordApplicationEmoji

Changed methods, properties & objects

• DiscordEmoji.RolesInternal - Will default to [] meaning RolesInternal.Roles should never throw an NRE. Made it internal
• DiscordEmoji.FromName(BaseDiscordClient client, string name, bool includeGuilds = true, bool includeApplication = true) - (DiscordEmoji) , can be casted to DiscordUnicodeEmoji, DiscordGuildEmoji & DiscordApplicationEmoji
• ⚠️ DiscordEmoji.TryFromName(BaseDiscordClient client, string name, bool includeGuilds, bool includeApplication, out DiscordEmoji emoji) - (DiscordEmoji) , can be casted to DiscordUnicodeEmoji, DiscordGuildEmoji & DiscordApplicationEmoji | Breaking: Additional required parameter bool includeApplication

Additional

• Updated incorrect internal documentation

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

@Aiko-IT-Systems/discatsharp

[TheXorog]

Rather minor nitpick

Resolved