Editor: Register the core entity actions on the server

[jorgefilipecosta]

Backports the PHP changes of WordPress/gutenberg#84660, a follow-up to #14276.

Gutenberg now registers the core actions (Trash, Rename, Duplicate…) on the server, through the entity actions API, and the editors read them from /wp/v2/entity-actions. This PR makes Core register them too.

This PR:

• Copies the PHP files of @wordpress/core-actions from the Gutenberg build to wp-includes/build/scripts/core-actions/, in the gutenberg-php copy task that copies routes.php and pages.php, and loads its index.php from wp-settings.php the same way.
• Adds _wp_preload_entity_actions(), which preloads the actions of the post type the post editor edits.
• Ports the tests of register_core_entity_actions(), without the "Duplicate…" action of posts, which is only registered in the Gutenberg plugin.

Some notes:

• This needs a Gutenberg pin that includes Core Actions: Register the core actions on the server gutenberg#84660, which comes in its own PR along with the files it generates. Until then wp-includes/build/scripts/core-actions/ doesn't exist, so the new tests are skipped and nothing is registered.
• The pin also needs Core Actions, Core Fields: Translate the labels with the default text domain gutenberg#85139, which removes the gutenberg text domain from the labels, so they are translated with the default one. The test_the_labels_are_translated_with_the_default_text_domain test covers it.
• With a pin at Gutenberg trunk, the actions also include "Set as homepage…" and "Set as posts page…" from Actions API: Register the homepage and posts page actions as entity actions gutenberg#84646. Only administrators get them, on pages.

Testing Instructions

1. Set gutenberg.sha in package.json to trunk, then run npm run gutenberg:download and npm run build:dev.
2. Open wp-admin/site-editor.php?p=%2Fpage. In the console, run await wp.apiFetch( { path: '/wp/v2/entity-actions?kind=postType&name=page' } ) and verify it returns the actions of pages and the @wordpress/core-actions/post_type_supports module.
3. On the same screen, verify the actions menus of a draft and a published page, and rename, trash, restore and permanently delete a page. In the patterns screen, rename and duplicate a pattern.
4. Open a page in the post editor and verify the actions menu of the inspector. Verify in the Network panel that the editor made no request to /wp/v2/entity-actions, which is preloaded.
5. Run npm run test:php -- --group entity-actions.

Gutenberg PR: WordPress/gutenberg#84660

Trac ticket: https://core.trac.wordpress.org/ticket/66343

Use of AI Tools

AI assistance: Yes
Used for: porting the code and the tests from the Gutenberg PR, and drafting this description; reviewed and edited by me.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[oandregal]

I've tested this as part of #14514

[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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jorgefilipecosta, oandregal.

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

[github-actions]

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 64566
GitHub commit: a9398d7

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.