[Bug] Add missing textarea control handler.

[theodesp]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

This PR adds a missing TextAreaControl within the custom block editorFields configuration.

Related Issue(s):

#1895

Testing

1. Inside the /example/next/block-support package add the following fields in the block-b Component.config that includes a control: 'textarea'

Component.config = {
  name: 'CreateBlockBlockB',
  editorFields: {
    message: {
      type: 'string',
      label: 'My Message',
      location: 'editor',
    },
    textArea: {
      type: 'string',
      label: 'My Message',
      location: 'editor',
      control: 'textarea'
    },
  },
};

Also update the block.json to recognize the new attribute

"attributes": {
		"message": {
			"type": "string",
			"default": "Hello World"
		},
		"textArea": {
			"type": "string",
			"default": "Hello World"
		},

2. Build and push the blocks to WordPress:

$ npm run blockset -w examples/next/block-support 

3. Inside the block editor you should be able to view the textArea field rendered as textarea control instead of being empty.

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 6b48c58

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@faustwp/block-editor-utils	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[ChrisWiegman]

LGTM