docs: use ESM code in examples

[MrMythicalYT]

Please describe the changes this PR makes and why it should be merged:
This PR converts the documentation examples from CommonJS to ESM.
Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• This PR only includes non-code changes, like changes to documentation, README, etc.

[vercel]

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

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
discord-js	⬜️ Ignored (Inspect)			Apr 20, 2023 6:37am
discord-js-guide	⬜️ Ignored (Inspect)			Apr 20, 2023 6:37am

[monbrey]

Is this the only file that needs this change?

[Jiralite]

Yeah, no other example uses require():

[almeidx]

Can you update these too?

discord.js/packages/discord.js/README.md

Lines 59 to 103 in a2ab2b8

	```js
	const { REST, Routes } = require('discord.js');
	const commands = [
	{
	name: 'ping',
	description: 'Replies with Pong!',
	},
	];
	const rest = new REST({ version: '10' }).setToken(TOKEN);
	(async () => {
	try {
	console.log('Started refreshing application (/) commands.');
	await rest.put(Routes.applicationCommands(CLIENT_ID), { body: commands });
	console.log('Successfully reloaded application (/) commands.');
	} catch (error) {
	console.error(error);
	}
	})();
	```
	Afterwards we can create a quite simple example bot:
	```js
	const { Client, GatewayIntentBits } = require('discord.js');
	const client = new Client({ intents: [GatewayIntentBits.Guilds] });
	client.on('ready', () => {
	console.log(`Logged in as ${client.user.tag}!`);
	});
	client.on('interactionCreate', async interaction => {
	if (!interaction.isChatInputCommand()) return;
	if (interaction.commandName === 'ping') {
	await interaction.reply('Pong!');
	}
	});
	client.login(TOKEN);
	```

[monbrey]

Can you update these too?

discord.js/packages/discord.js/README.md

Lines 59 to 103 in a2ab2b8

	```js
	const { REST, Routes } = require('discord.js');
	const commands = [
	{
	name: 'ping',
	description: 'Replies with Pong!',
	},
	];
	const rest = new REST({ version: '10' }).setToken(TOKEN);
	(async () => {
	try {
	console.log('Started refreshing application (/) commands.');
	await rest.put(Routes.applicationCommands(CLIENT_ID), { body: commands });
	console.log('Successfully reloaded application (/) commands.');
	} catch (error) {
	console.error(error);
	}
	})();
	```
	Afterwards we can create a quite simple example bot:
	```js
	const { Client, GatewayIntentBits } = require('discord.js');
	const client = new Client({ intents: [GatewayIntentBits.Guilds] });
	client.on('ready', () => {
	console.log(`Logged in as ${client.user.tag}!`);
	});
	client.on('interactionCreate', async interaction => {
	if (!interaction.isChatInputCommand()) return;
	if (interaction.commandName === 'ping') {
	await interaction.reply('Pong!');
	}
	});
	client.login(TOKEN);
	```

If you're updating that part of the README, it should probably align with my changes to the command deployment in the guide: https://github.com/discordjs/discord.js/pull/9385/files#diff-af7cad8eaebbb884ba861e35ce70fd37dcb6d78b8a491cd986356971b29fd4b9

Not the same level of detail, but use top-level-await, the Events enum instead of string events

[kyranet]

Sweet TLA.