Jetpack AI: Allow non admin users

[renatoagds]

Update the way we handle data and block interface on Jetpack AI. Right now, we look if the current user is connected, but if the user isn't an admin, it won't be connected, but the site will be. Since Jetpack AI is site-based and not user-based, we should to make our logic site-based.

More context: pe4Cmx-37K-p2

Proposed changes:

• Move all connection manager logic to check for is_connected.
• Move all UI logic to check for isRegistered.
• Remove the permission_callback for ai-assistant-feature request.

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

pe4Cmx-37K-p2

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

N/A

Testing instructions:

Since we're changing the way we block/allow things, we need to review all our features and test them with both admin and non-admin users (like editors).

Below is a list of our current features:

• AI Assistant Block
• Voice to Content
• Excerpt
• Post Feedback
• Write Brief
• SEO Enhancer
• Title Generation
• AI Image
• Text Block Extension
• Image Block Extension

Please go through all these features and play with admin, non-admin users, and not connected site.

[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 Review, ...).
  
• 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

No scheduled milestone found for this plugin.

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

[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 WoA dev 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 (Jetpack), and enable the feature/ai-assistant-editor branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack feature/ai-assistant-editor

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/extensions/blocks/ai-assistant/extensions/lib/can-ai-assistant-be-enabled.ts	0/16 (0.00%)	0.00%	1 ❤️‍🩹
projects/plugins/jetpack/_inc/lib/class-jetpack-ai-helper.php	0/206 (0.00%)	0.00%	-5 💚

Full summary · PHP report · JS report