Command localizations don't use camelcase when creating a command with slashcommand builder

[schblondie]

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

Status and versioning classification:

• I know how to update typings and have done so, or typings don't need updating
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed) - Not sure if breaking change, because technically object keys changed

[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	Jan 23, 2023 at 11:42AM (UTC)

[vercel]

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

A member of the Team first needs to authorize it.

[Jiralite]

Builders is not solely used with discord.js, which makes this pull request incorrect. In addition, changing the casing in discord.js is also wrong, as we are receiving that data from Discord.

[almeidx]

The Discord API data comes with camel-cased keys

[schblondie]

This is true, I apologize.
But when you compare line 78 with line 88 you can see that the this.nameLocalized is also in correct camel case even when getting the non camel case value data.name_localized

[schblondie]

I adjusted the code making sure it doesn't conflict with the Discord API.

Now only the SlashCommandBuilder & ContextMenuBuilder Data is in camelCase which doesn't matter when accessing the API as the functions transformCommand() (packages\discord.js\src\managers\ApplicationCommandManager.js - line 233) and transformOption() (packages\discord.js\src\structures\ApplicationCommand.js - line 549) make sure that the keys are in the appropriate case.