Add entity type for individual Term objects

[fabiankaegy]

What?

Adds a new Term type to the available entity types exported from the core-data package.

Why?

' getEntityRecord' is commonly used to deal with individual terms outside of any taxonomy. Currently, we don't expose any types for it.

How?

Adding the type to the correct folder and exporting it.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
Co-authored-by: tyxla <tyxla@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

Unfortunately, I'm not the best person to review TS changes.

cc @tyxla, @jsnajdr

[tyxla]

This looks pretty good, thanks @fabiankaegy 🙌

The primary thing that we should check is whether we're correctly providing the context of each field. Or perhaps you're intentionally skipping them?

Other than that, I think this is good to go!

[tyxla]

Isn't meta essentially an associative array of meta fields? And because of the database schema, they'll always end up strings?

Also it supports view and edit contexts, right?

Suggested change

	meta: { [ key: string ]: unknown };
	meta: ContextualField<
	Record< string, string >,
	'view' | 'edit',
	C
	>;

[tyxla]

According to the REST API docs, this can be available in multiple contexts:

Suggested change

	name: string;
	name: ContextualField< string, 'view' | 'embed' | 'edit', C >;

[tyxla]

Same as above:

Suggested change

	slug: string;
	slug: ContextualField< string, 'view' | 'embed' | 'edit', C >;

[tyxla]

I've always found the "alphanumeric" description ambiguous, considering that terms can also contain dashes.

[tyxla]

I'd suggest auditing all fields for context. count seems to be available for view and edit and not for embed.