feat(additional-info): add more breaking changes

Author: sdanialraza

guide/additional-info/updating-from-v14.md

@@ -14,6 +14,10 @@ Make sure you're using the latest LTS version of Node. To check your Node versio
 
 `ApplicationCommand#dmPermission` and `ApplicationCommand#setDMPermission()` have been removed. This was legacy functionality for commands—use contexts instead.
 
+### ApplicationCommandManager
+
+`ApplicationCommandManager#fetch()` method has been updated for consistency with other managers. Previously, it accepted two parameters: `id` (a snowflake or an options object) and an `options` object. Now, it only accepts a single `options` argument, which can be a snowflake or an options object that may include an `id` property.
+
 ### AnnouncementChannel
 
 `AnnouncementChannel#addFollower()` now returns `FollowedChannelData` instead of a snowflake. This helps to expose the created webhook id in the target channel.
@@ -24,6 +28,10 @@ Make sure you're using the latest LTS version of Node. To check your Node versio
 
 ### Client
 
+#### Emojis
+
+`Client#emojis` has been removed due to confusion with the introduction of application emojis and performance impact. Use `resolveGuildEmoji` utility function to get a cached guild emoji.
+
 #### Ping
 
 `Client#ping` has been added to replace the old `WebSocketManager#ping`. This will be `null` when the heartbeat from the gateway is yet to be received.
@@ -67,6 +75,10 @@ The underlying WebSocket behaviour has changed. In version 14, this was a non-br
 - [discordjs/discord.js#10420](https://github.com/discordjs/discord.js/pull/10420)
 - [discordjs/discord.js#10556](https://github.com/discordjs/discord.js/pull/10556)
 
+### ClientEvents
+
+`ClientEvents` type has been removed. Use `ClientEventTypes` instead. This change ensures consistency with the rest of the event types across the library.
+
 ### ClientOptions
 
 Removed `ClientOptions#shards` and `ClientOptions#shardCount` in favor of `ClientOptions#ws#shardIds` and `ClientOptions#ws#shardCount`.
@@ -210,6 +222,10 @@ There are two ways to achieve the same behaviour, so the "helper" option has bee
 + const { message } = response.resource;
 ```
 
+#### GuildMemberResolvable
+
+`GuildMemberResolvable` type has been removed. It was defined as `GuildMember | UserResolvable`, but `UserResolvable` already includes `GuildMember`. Use `UserResolvable` instead.
+
 #### Premium response type
 
 Discord no longer supports the `PREMIUM_REQUIRED` interaction response type. In the past, you would have done this: