Break out the Curating the Editor Experience doc into its own How-to Guides section

[ndiego]

This PR is an initial implementation of the concept outlined in #56170.

V1: Divide and solidify

Break each logical section into individual pages (locking APIs, providing default controls/options, etc) and add in more content/links to articles/video that we already have from the Developer Blog (no new content!).

I have taken the Curating the Editor Experience doc and made it its own section in How-to Guides. I have then broken the doc up into five additional docs.

1. Block locking
2. Patterns
3. theme.json
4. Filters and hooks
5. Disabling Editor functionality

The last section is a bit of a catch-all that covers miscellaneous curation techniques not covered in the other sections. I did add some new content here about disabling block variations and styles.

Let me know what you think of this initial iteration. The next step will be to go through each sub-doc and overhaul the content with additional information, new examples, etc.

[github-actions]

Flaky tests detected in 5f4ad6c.
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/7281194916
📝 Reported issues:

• [Flaky Test] Should show Columns block only if selected blocks are between limits (1-6) #40369 in specs/editor/various/block-switcher.test.js

[annezazu]

Approving but left two minor comments :) Thank you for moving this forward.

[annezazu]

Find the lower case t to throw me off here. Any reason not to capitalize?

[justintadlock]

I haven't tested across different systems, but I'd always err on the side of preserving the correct case for filenames.

[ndiego]

I haven't tested across different systems, but I'd always err on the side of preserving the correct case for filenames.

Yeah, we are doing the same thing with other common filenames like block.json, functions.php, etc. That said, we do need to comb through the Handbook and standardize this.

[annezazu]

🥳 Thanks for getting this done!