refactor: separate MESSAGE_CREATE fields from APIMessage object

[vvito7]

Please describe the changes this PR makes and why it should be merged:
Separates MESSAGE_CREATE and MESSAGE_UPDATE fields from APIMessage object.

If applicable, please reference Discord API Docs PRs or commits that influenced this PR:

• Separate event specific fields from the Message object discord/discord-api-docs#4915

[vladfrangu]

Can you ensure the PR is up to date with the upstream PM? Let me know, and I'll merge it

[vvito7]

What do you think of transforming this (extra fields):

	/**
	 * ID of the guild the message was sent in
	 */
	guild_id?: Snowflake;
	/**
	 * Member properties for this message's author
	 *
	 * The member object exists in `MESSAGE_CREATE` and `MESSAGE_UPDATE` events
	 * from text-based guild channels
	 *
	 * See https://discord.com/developers/docs/resources/guild#guild-member-object
	 */
	member?: APIGuildMember;
	/**
	 * Users specifically mentioned in the message
	 *
	 * The `member` field is only present in `MESSAGE_CREATE` and `MESSAGE_UPDATE` events
	 * from text-based guild channels
	 *
	 * See https://discord.com/developers/docs/resources/user#user-object
	 * See https://discord.com/developers/docs/resources/guild#guild-member-object
	 */
	mentions: (APIUser & { member?: Omit<APIGuildMember, 'user'> })[];

into an interface? Since we are using it twice, in the create and update event.

And also, should this kind of comment "The member object exists in MESSAGE_CREATE and MESSAGE_UPDATE events from text-based guild channels" be keep in both tables? For example the mentions field.

[vercel]

@vvito7 is attempting to deploy a commit to the Sapphire Team on Vercel.

A member of the Team first needs to authorize it.

[vladfrangu]

into an interface? Since we are using it twice, in the create and update event.

sure

And also, should this kind of comment "The member object exists in MESSAGE_CREATE and MESSAGE_UPDATE events from text-based guild channels" be keep in both tables? For example the mentions field.

Sure

[vvito7]

Can you ensure the PR is up to date with the upstream PM? Let me know, and I'll merge it

Hopefully everything is ok now