AI Client: Separate AIControl UI from block logic and update messages

[dhasilva]

Fixes #36966

Proposed changes:

• Separates the AIControl component into a base AIControl, a block-specific BlockAIControl component and an extension-specific ExtensionAIControl. This allows us to reuse the same base for the extensions input, which looks very similar but has different actions and behavior
• Updates the messages, adding a Storybook story
• Updates the Storybook story for the AIControl component and the two new components

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• ( cd projects/js-packages/storybook && pnpm run storybook:dev --no-open --debug-webpack ) to run Storybook
• Go to JS Packages > AI Client
• Check the Messages story with 3rftFw1oBgRusMWgfNTaVz-fi-4437_5481
• Check the AIControl, BlockAIControl and ExtensionAIControl stories
• Use the AI Assistant and AI Form blocks, check that the buttons and behaviors (loading, disabled, etc) are working as normal

At this point the new ErrorMessage will not replace the errorComponent for the block control. That will be done later to keep compatibility.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the update/jetpack-ai-input-ui branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/jetpack-ai-input-ui
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/jetpack-ai-input-ui
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen daily.
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for May 7, 2024 (scheduled code freeze on May 6, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[vianasw]

This is looking super nice! Storybook stories seem all fine but I'll defer to someone else to review the code more thoroughly.

[renatoagds]

Are we planning to use this in more than one place? Could be a discussion about keeping it in the package or not (not for this PR)

[dhasilva]

That is a very good catch. I'd also prefer to have this on the ai-assistant folder instead of the package.
Maybe we can have a call with @lhkowalski to decide where to move this and the other components as a last task?

[renatoagds]

Maybe we can have a call with @lhkowalski to decide where to move this and the other components as a last task?

Yes, for sure. Let's do it.