Fixes block-editor component index to export ButtonBlockAppender with correct name

[gaavar]

Fixes block-editor's component index to export ButtonBlockAppender with the correct name (#25885)

Description

Revised block-editor's component index to export ButtonBlockAppender with the correct name.
ButtonBlockAppender was earlier exported with the incorrect name ButtonBlockerAppender.

Deprecated ButtonBlockerAppender.

How has this been tested?

Screenshots

Types of changes

Bug fix

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

[talldan]

@gaavar Thanks for picking this up!

I think there are two things to address.

Unfortunately there might be plugins importing/using ButtonBlockerAppender, so we should continue to export it. It could be deprecated. That's done by calling the deprecate function. The following will output a console warning:

import deprecated from '@wordpress/deprecated';

deprecated( 'wp.blockEditor.ButtonBlockerAppender', {
	alternative: 'wp.blockEditor.ButtonBlockAppender'
} );

The tricky bit is that the message should only be shown if the user imports ButtonBlockerAppender, so I think you'd want to wrap ButtonBlockAppender, a bit like the following code elsewhere in the codebase, and then export that as ButtonBlockerAppender 😄 :

gutenberg/packages/editor/src/components/deprecated.js

Lines 66 to 72 in b52d33b

	const Component = forwardRef( ( props, ref ) => {
	deprecated( 'wp.editor.' + name, {
	alternative: 'wp.blockEditor.' + name,
	} );
	return <Wrapped ref={ ref } { ...props } />;
	} );

The second thing is that there's some documentation associated with the components that needs to be regenerated (which is why the 'Static Analysis' task is failing). It can be regenerated by running npm run docs:build locally and then committing and pushing the results.

[talldan]

@gaavar I think there's some misunderstanding of my comment. The deprecation for ButtonBlockerAppender will have to be in the packages/block-editor/src/components/index.js file. I think it's fine to copy some of the code over for deprecating the component from the other file.

[chrisvanpatten]

@gaavar Any concern if I pick this task up?