feat: discord.js v15

[Jiralite]

Description

Important

Before merging, a v14 branch should be created.

This pull request can be accessed at https://v15.discordjs.guide. Feel free to open pull requests to this branch, suggest changes on this pull request, drop comments about the guide that needs updating, etc.

TODO

• feat(NewsChannel)!: return followed channel data discord.js#8566
• feat(InteractionResponses)!: support with_response query parameter discord.js#10499
• refactor!: remove discord.js builders discord.js#10529
• fix(GuildAuditLogEntry)!: Fix some incorrect types and runtime logic discord.js#10591
• refactor!: Remove deprecations discord.js#10647
• refactor!: replace isAnySelectMenu with isSelectMenu discord.js#10656
• refactor!: use AsyncEventEmitter instead of EventEmitter discord.js#10710
• types!: remove GuildMemberResolvable discord.js#10713
• refactor!: return void on bans/kick/addRole/removeRole methods discord.js#10714
• refactor!: consolidate parameters into a single options object discord.js#10718
• refactor(Client)!: Remove emojis getter discord.js#10754

[Amgelo563]

Looks like the What's new page still needs updating, though is that really needed? I'd argue it could be removed, I don't think it's that useful for users, since they mostly only concern about what changed in djs, not the guide.

[Jiralite]

Might be a question for @almostSouji.

My thoughts: that entire page is outdated. Not sure if we want to keep it updated, though.

[almostSouji]

i'm good with removal, if you think it serves little to no benefit atm @Jiralite. we can always re-introduce it if there are notable changes we feel would benefit from being listed in an overview
in the iteration the page was introduced in a bunch of things changed structurally and discord introduced an amount of new core concepts which we chose to cover

[almostSouji]

this will have to be ported to the new guide framework and mono repository, or be considered as a new foundation for the next iteration of the guide, rather than an update (we will still need a "changes in..." guide to ease the transition for folks switching, of course)