Rename wp_register_block_template() to register_block_template()

[Aljullu]

What?

As discussed in #61577, we want to remove the wp_ prefix from wp_register_block_template() and wp_unregister_block_template().

Backport PR in core: WordPress/wordpress-develop#7543.

Why?

To keep it consistent with other functions like register_block_type, register_block_pattern and register_block_style.

How?

This PR directly replaces the old functions with the new ones, it doesn't deprecate them. Given that they were not shipped in WordPress core my understanding is that we don't need to keep backwards compatibility. But please, correct me if I'm wrong.

Testing Instructions

1. Add this code to an existing plugin or in a code snippet using the Code Snippets plugin:

add_action(
	'init',
	function () {
		register_block_template(
			'gutenberg//plugin-template',
			array(
				'title'       => 'Plugin Template',
				'description' => 'A template registered by a plugin.',
				'content'     => '<!-- wp:template-part {"slug":"header","tagName":"header"} /--><!-- wp:group {"tagName":"main","layout":{"inherit":true}} --><main class="wp-block-group"><!-- wp:paragraph --><p>This is a plugin-registered template.</p><!-- /wp:paragraph --></main><!-- /wp:group -->',
			)
		);
		add_action(
			'category_template_hierarchy',
			function () {
				return array( 'plugin-template' );
			}
		);
	}
);

2. Go to a post category in the frontend (ie: /category/test-category/) and verify the Plugin Template contents are rendered.
3. Go to Appearance > Editor > Templates and verify the Plugin Template appears with the correct title and description.
4. Make some edits to the template. Verify they are applied in the frontend.
5. Revert the edits and verify edits are reverted in the frontend as well.
6. Edit the previous code snippet adding these lines:

		unregister_block_template( 'gutenberg//plugin-template' );

7. Verify the template no longer appears under Appearance > Editor > Templates and going to a post category in the frontend doesn't render it either.

[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: Aljullu <aljullu@git.wordpress.org>
Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: ndiego <ndiego@git.wordpress.org>
Co-authored-by: getdave <get_dave@git.wordpress.org>

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

[github-actions]

Flaky tests detected in f942c09.
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/11244989720
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js

[youknowriad]

LGTM 👍

[youknowriad]

Any concerns @peterwilsoncc @ndiego

[ndiego]

Any concerns @peterwilsoncc @ndiego

Not on my end, as I would consider this fixing a "bug" in the original implementation, but I have alerted the other 6.7 release leads in WP Slack and will follow up when there is a consensus.

[getdave]

I'd consider this fixing a bug 👍

[ndiego]

I'd consider this fixing a bug 👍

Given the 👍 on this comment above. I have no concerns moving forward.

As an aside, this change will be highlighted in the What's new for developers article later this week on the Developer Blog.

[getdave]

According to the docs we will also need to raise a Core PR to manually back port these changes to WP Core. cc @kevin940726 for confidence check.

[Aljullu]

According to the docs we will also need to raise a Core PR to manually back port these changes to WP Core. cc @kevin940726 for confidence check.

The WP core backport PR is this one: WordPress/wordpress-develop#7543. Sorry I forgot to add the link in the PR description. 😅

[github-actions]

I just cherry-picked this PR to the wp/6.7 branch to get it included in the next release: ffb2e13