Docs: Remove misleading section from curating the editor experience

[Mamaduka]

What?

Closes #63822.

PR removes the misleading "Disable access to the Template Editor" section from curating the editor experience documentation page.

Why?

Removing theme support for block-templates entirely disables block templates for a theme, including rendering them on the frontend. The theme support flags shouldn't be used to restrict access to certain editor features.

Testing Instructions

None.

[fabiankaegy]

I agree the way it is written there today is very misleading.

I do think there is value in removing this theme support in classic themes which is why it was added. But that isn't clear from the section.

[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: Mamaduka <[email protected]>
Co-authored-by: fabiankaegy <[email protected]>
Co-authored-by: carolinan <[email protected]>
Co-authored-by: andreawetzel <[email protected]>

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

[Mamaduka]

I do think there is value in removing this theme support in classic themes which is why it was added. But that isn't clear from the section.

Right, it's not related to curating the editor experience. It's more of a theme configuration when a classic theme wants to use the theme.json, but opts out of the block templates support.

The theme handbook might be a better place to document this.