HTML API: Pull in updates from Core

[dmsnell]

What?

Blessed update pulling in updates to the HTML Tag Processor from Core into Gutenberg.

Related: WordPress/wordpress-develop@455b1e8

Why?

This process is being explored post 6.2 merge now that the HTML API development is occurring in Core.

Testing

Unit tests should pass, code should be audited. These changes should reflect the files in Core. They were generated by copying those files directly and then running git a -p to include everything but the class rename.

For the updates that landed here in Gutenberg head of Core (assuming those changes migrate into Core once the window for changes opens) I followed this procedure:

• Temporarily revert 0ff570f
• Copy the Tag Processor for Core's repo
• git add -p to include only the updates
• Commit in a temporary branch: note the commit hash
• Reset to trunk
• git cherry-pick the commit hash from the temporary branch

There were no merge conflicts this way, and I luckily didn't have to manually handle the addition of has_bookmark in Gutenberg.

[github-actions]

Flaky tests detected in 17ef976f7057b46b22efe80272ef7481f3054a77.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4368732969
📝 Reported issues:

• [Flaky Test] shouldn't conflict with server-side autosave #35176 in specs/editor/various/autosave.test.js

[dmsnell]

@ockham @ockham seems like we could use a few canary tests in the compat layer to ensure basic operation (e.g. we don't introduce syntax errors on these backports)

I think that with the work done lately to run PHP tests against a matrix of versions we might be able to do this once and have it check the 6.2 and 6.3 compat classe.

I'll try to add them and explore

[dmsnell]

Updated from fe3f85e to 15822ed to also pull in the documentation changes. Followed the same method mentioned in the description.

[adamziel]

Thank you @dmsnell !