feat(Client): guildAuditLogEntryCreate event

[almeidx]

Please describe the changes this PR makes and why it should be merged:
Implements basic support for the GUILD_AUDIT_LOG_ENTRY_CREATE event

Changes:

• Add Client#guildAuditLogEntryCreate event
• GuildAuditLogsEntry#targetId and GuildAuditLogsEntry#executorId to address feat(Client): guildAuditLogEntryCreate event #9058 (comment)
• Moved logs to the last constructor parameter of GuildAuditLogsEntry (which is private) so as to not make it nullable (we don't received it via the gateway)

Upstream:

• Add GUILD_AUDIT_LOG_ENTRY_CREATE event discord/discord-api-docs#5849

Status and versioning classification:

• I know how to update typings and have done so, or typings don't need updating

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
discord-js	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 17, 2023 at 8:12PM (UTC)
discord-js-guide	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 17, 2023 at 8:12PM (UTC)

[Jiralite]

Should update the list of intents too via the issue tracker.

[Jiralite]

This doesn't work because the gateway event is called GUILD_AUDIT_LOG_ENTRY_CREATE but this is looking for AUDIT_LOG_ENTRY_CREATE.

[Jiralite]

I seem to have found a bug with this event. Use this very basic code sample:

import { Client, Events, GatewayIntentBits } from "discord.js";

const client = new Client({ intents: GatewayIntentBits.Guilds | GatewayIntentBits.GuildBans });

client.on("raw", console.log);
client.on(Events.AuditLogEntryCreate, console.log);

client.login();

Upon pinning a message, this event will be received:

{
  t: 'GUILD_AUDIT_LOG_ENTRY_CREATE',
  s: 6,
  op: 0,
  d: {
    user_id: 'user_id',
    target_id: 'target_id',
    options: {
      message_id: 'message_id',
      channel_id: 'channel_id'
    },
    id: 'id',
    action_type: 74,
    guild_id: 'guild_id'
  }
}

When discord.js constructs a GuildAuditLogsEntry out of it, GuildAuditLogsEntry#executor and GuildAuditLogsEntry#target are both undefined.

You can see how these are defined here:

discord.js/packages/discord.js/src/structures/GuildAuditLogsEntry.js

Lines 127 to 131 in 13ce78a

	this.executor = data.user_id
	? guild.client.options.partials.includes(Partials.User)
	? guild.client.users._add({ id: data.user_id })
	: guild.client.users.cache.get(data.user_id)
	: null;

discord.js/packages/discord.js/src/structures/GuildAuditLogsEntry.js

Lines 292 to 297 in 13ce78a

	} else if (targetType === Targets.Message) {
	// Discord sends a channel id for the MessageBulkDelete action type.
	this.target =
	data.action_type === AuditLogEvent.MessageBulkDelete
	? guild.channels.cache.get(data.target_id) ?? { id: data.target_id }
	: guild.client.users.cache.get(data.target_id);

When audit logs are fetched (as they have been all this time), Discord sends across the user objects that the audit log references and we store them safely away. However, the gateway does not do this. These are now potentially undefined and the same may go for application commands, auto moderation rules, scheduled events, integrations, threads, and webhooks. Currently, these are typed as always present, but they are documented as nullable, so that is good for now. The typings for this are somewhat complex, though.

[vercel]

@almeidx is attempting to deploy a commit to the discordjs Team on Vercel.

A member of the Team first needs to authorize it.