feat: add components to /builders

[suneettipirneni]

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

Adds all current component types to /builders.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)

[vladfrangu]

Looks fine to me. Can you not implement something similar to application command options (relating to the toJSON() being mostly {...this}?

[suneettipirneni]

Looks fine to me. Can you not implement something similar to application command options (relating to the toJSON() being mostly {...this}?

I can, I just didn't know if handling snake_case like this:

{
	...this
    snake_case_prop: this.camelCaseProp,
}

was preferred or not

[vladfrangu]

It's what I did for builders (and subsequently forgot to do consistently), but CC @discordjs/the-big-4 about this

[suneettipirneni]

It's what I did for builders (and subsequently forgot to do consistently), but CC @discordjs/the-big-4 about this

Also I just realized that if there are snake_case keys, and you do ...this you'll have the leftover camelcase key in the json. So that'll also have to be manually deleted off the object.

[vladfrangu]

It's what I did for builders (and subsequently forgot to do consistently), but CC @discordjs/the-big-4 about this

Also I just realized that if there are snake_case keys, and you do ...this you'll have the leftover camelcase key in the json. So that'll also have to be manually deleted off the object.

Just replace all camelCase props on the class with snake_case 🦐

[iCrawl]

This needs a rebase.

[SpaceEEC]

Are the changes to the yarn.lock file intentional? 👀

[suneettipirneni]

Note: CI failing because of voice tests