Template field: Remove dependency with the "settings" object

[snehapatil2001]

What?

Resolves #67521.

Improve the Template field in the post-edit screen by removing its dependency on block editor settings and fetching template data directly from core-data.

Why?

• The current implementation of the Template field requires wrapping with ExperimentalBlockEditorProvider and depends on block editor settings, which creates unnecessary complexity and hidden dependencies.
• This change addresses the issue described in Gutenberg Issue #67521, where the Template field should work independently without requiring specific provider wrapping.

How?

• Created a custom useTemplates hook to fetch template records directly from core-data
• Removed dependency on ExperimentalBlockEditorProvider
• Modified the Template field's Edit component to receive templates as a prop
• Simplified the template data fetching process
• Ensured the Template field can be used without additional context or settings

Testing Instructions

1. Open the post/page editor
2. Navigate to the post settings sidebar
3. Verify the Template dropdown appears and is populated
4. Select different templates and ensure they can be applied
5. Test with both single and multiple post editing scenarios

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

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

[gigitux]

Thank you for working on this issue!

The template field should function independently of any data passed through PostEditForm. All data fetching should be handled within the template-edit file.

I followed the testing instructions and I got some errors:

Screen.Capture.on.2024-12-04.at.17-08-25.mov

Upon further investigation, it appears that the main issue is that multiple core blocks, such as AvatarBlock, depend on the settings object. Without ExperimentalBlockEditorProvider in this context, the settings object is unavailable.

I think that fixing #67521 removing any dependency with the settings object could not be a straightforward task given that it would require the refactor of multiple blocks.

@youknowriad could have better context on this.