refactor: switch api and gateway to V8

[NotSugden]

Please describe the changes this PR makes and why it should be merged:
resolves #4669

V8 diff - discord/discord-api-docs@545ff4a

Changes currently in this PR:

• A couple minor documentation fixes
• Bumped Gateway and REST versions to 8
• Modifies BitField to support BigInts and Permissions to use them
• Stops the channelCreate event emitting for DM Channels as that behaviour seems to have been removed
  • channelDelete still emits, so that's been left as-is
• Roles are no longer used to update a GuildMember with the Presence Update event as the roles are no longer sent
• Fixed an error that would show double stack trace
• Updated presence updating methods to use only the data available for a Presence Update
  • Along with this said functions are no longer async
• Documented ClientUser#edit
• Removed Guild#embed* in favour of Guild#widget*
• Fixed a couple documentation typos
• Added new OverwriteTypes constant to match API Change
• Changed a few methods to be async
• Removed ClientOptions#ws#intents and replaced it with ClientOptions#intents, and made it required as the V8 Gateway requires them
• Documented new error codes
• Removed options from Guild#fetchIntegrations() as the query parameter was removed in V8 (Add v8 integration changes to changelog discord/discord-api-docs#2238)
  • also made the function async
• Made GuildChannel#updateOverwrite() async
• Made PermissionOverwrites#update() async
• Made PermissionOverwrites#delete() async
• Updated tests to use non-privileged intents

Notes about the non-usage of BigInt literals

The usage of BigInt Litertals is due to a bug with the library handling the jsdoc, failing the CI

Status

• Code changes have been tested against the Discord API, or there are no code changes
  • I haven't experienced any 'broken' behaviour, but if anyone would like to double check thats fine by me
• I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

• This PR changes the library's interface (methods or parameters added)
  • This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• This PR only includes non-code changes, like changes to documentation, README, etc.

[advaith1]

imo:

• ClientOptions#intents should work for setting intents, like the other options that are intended to be changed (and are not sent raw)
• we should not be setting any default intents, bot devs should have to put the intents they need, otherwise, this basically removes the whole point of intents

[papaia]

Reflecting the second point in #4879 (comment).

[NotSugden]

imo:

• ClientOptions#intents should work for setting intents, like the other options that are intended to be changed (and are not sent raw)
• we should not be setting any default intents, bot devs should have to put the intents they need, otherwise, this basically removes the whole point of intents

sorry that took so long, but resolved in 9db4acc

[vladfrangu]

This PR will need extensive testing before merging 🙏

Some nitpicks for now

[NotSugden]

ok! i've done a quick test and everything seems to be working fine now, if anyone else wants to confirm that feel free, marking as ready for review ig

[vladfrangu]

This PR is not ready. There are REST changes that need to be done to account for the ratelimits finally respecting specs...

[iCrawl]

@NotSugden this needs a rebase

[NotSugden]

@iCrawl done

[vaporoxx]

next to that, should options.intents really be required? (i.e. WebhookClients, i don't know if those actually use intents)

[NotSugden]

next to that, should options.intents really be required? (i.e. WebhookClients, i don't know if those actually use intents)

i have made a new type WebhookClientOptions (which is just a Pick of all applicable options from ClientOptions)

[Fyko]

discord.js/typings/index.d.ts

Line 2901 in 3e11c3b

interface PermissionFlags extends Record<PermissionString, number> {}

needs to be updated to

interface PermissionFlags extends Record<PermissionString, bigint> {}

[NotSugden]

rebased & suggested changes applied

[NotSugden]

fixed the docs error 🎉

[vladfrangu]

As a note for maintainers, however, please make sure this PR has been tested across everything it modifies before merging 🙏

[typpo]

I have tested message create, react, edit, and delete rate limits on @NotSugden's branch and had no problems :)

Stale

[SpaceEEC]

🎉

[JMTK]

After this was merged, my bot user is unable to initially receive DMs. If I send myself a message using an eval command from the bot, then it will start receiving messages. Is this expected given the bullet point channelCreate events are no longer emitted for DMs?

I sent myself "hi" from a Guild channel instead client.users.cache.get(message.author.id).send('hi'). After that, I received message events from my user.

Should I open an issue ticket?

[advaith1]

you can fix it by enabling the CHANNEL partial; we should make that always on (should have been in this pr)