AI Assistant: Remove autofocus on extended blocks while previewing

[dhasilva]

Fixes #39144

Proposed changes:

• Uses the extended blocks' isSelectionEnabled value to determine if autofocus should happen or not

The issue is caused by autofocus happening within the preview block. We want to keep the behavior on blocks added to the editor, but not for preview blocks.

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:

• Test using Firefox
• Go to the block editor
• Open the block inserter in the sidebar (The + button on the top left, after the site logo)
• Type "contact form"
• Check that the block inserter works as expected and the search input is not unfocused
• In the editor, add a Form block
• Check that the input is focused immediately
• Add a paragraph
• On the paragraph's block toolbar, click on the AI icon > "Ask AI Assistant"
• Check that the input is focused as well

Before	After
Peek.2024-09-03.19-08.mp4	Peek.2024-09-03.19-09.mp4

[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 fix/jetpack-ai-preview-focus branch.

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

  bin/jetpack-downloader test jetpack fix/jetpack-ai-preview-focus
  

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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

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 none scheduled (scheduled code freeze on undefined).

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

[sergeymitr]

Works well as far as I can tell.
@monsieur-z you know a lot more about the issue, can you please take a look as well.

[CGastrell]

Worked fine for me, code looks good

[dhasilva]

Merged to avoid a conflict with another PR. @monsieur-z, let me know if you think something else needs to be changed.