[core-data] Document and add types for dynamic actions and selectors.

[manzoorwanijk]

What?

Define the type declarations for dynamic selectors and actions for core-data package`

Why?

The dynamic selectors cause errors when used in TypeScript because TS can't find those defined anywhere.

How?

The PR creates TS definition declarations for all the dynamic selectors and some useful actions

Testing Instructions

• Use the dynamic selectors or actions in TypeScript files
• Confirm that TS doesn't show an error

Example

import { store as coreStore } from '@wordpress/core-data';
import { select } from '@wordpress/data';

const { getUser, getUsers } = select( coreStore );

Testing Instructions for Keyboard

Screenshots or screencast

We will now have auto-completions for entity selectors

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[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: manzoorwanijk <[email protected]>
Co-authored-by: sirreal <[email protected]>

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

[manzoorwanijk]

The description of these fields is copied from core REST API schema.