docs: Remove JSONEncondable

[Jiralite]

Please describe the changes this PR makes and why it should be merged:
I think we should stop referencing this TypeScript interface in our JavaScript documentation.

Look at this:

discord.js/packages/discord.js/src/structures/ActionRowBuilder.js

Lines 19 to 31 in 1b9d07f

	/**
	* Creates a new action row builder from JSON data
	* @param {JSONEncodable<APIActionRowComponent<APIActionRowComponentTypes>>
	* |APIActionRowComponent<APIActionRowComponentTypes>} other The other data
	* @returns {ActionRowBuilder}
	*/
	static from(other) {
	if (isJSONEncodable(other)) {
	return new this(other.toJSON());
	}
	return new this(other);
	}
	}

JSONEncodable<APIActionRowComponent<APIActionRowComponentTypes>>|APIActionRowComponent<APIActionRowComponentTypes>. Well damn. This is the same type duplicated with JSONEncodable.

The proposed modification: ActionRow|ActionRowBuilder|APIActionRowComponent. Wow, much more understandable, right?

JavaScript users only need to know what they can pass without needing to deeply understand all associated typings. One may pass a received (immutable) ActionRow from the API, an ActionRowBuilder, or use raw API data. This is the exact same behaviour from before but is documented in a simpler way that could be understood with ease.

I believe this change will allow users to understand this part of the documentation better.

Status and versioning classification:

• 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 ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
discord-js-guide	⬜️ Ignored (Inspect)			Apr 8, 2023 9:52pm

[vercel]

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

A member of the Team first needs to authorize it.