Jetpack SEO: Ensure more performant practices when getting enabled features.

[coder-karen]

Fixes #43033

Proposed changes:

• This PR changes how getEnabledFeatures works by making sure we only run the selector function if the dependencies have changed.
• This change was prompted by a useSelect warning in the console of post editors (when script debug is enabled, running WordPress 6.8):

The 'useSelect' hook returns different values when called with the same state and parameters.
This can lead to unnecessary re-renders and performance issues if not fixed.`
Non-equal value keys: enabledFeatures

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

p1744303609023589-slack-C02TQF5VAJD

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

No.

Testing instructions:

This may need expansion, but:

• If you spin up a Jurassic Ninja site using the Jetpack Beta tester plugin (testing in bleeding edge), and also install the WordPress Beta Tester plugin, with Jetpack connected you should be able to replicate the console warning if opening up a post. You will also need script debug enabled in wp-config.php: define( 'SCRIPT_DEBUG', 'true' );.

• With this PR applied, the warning no longer appears.

• To confirm no impact on features, activate SEO from the SEO panel (in the Jetpack sidebar), and 'generate metadata'.

[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 fix/jetpack-seo-getEnabledFeatures branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/jetpack-seo-getEnabledFeatures

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 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:

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

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: May 6, 2025
  • Code freeze: May 5, 2025

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/extensions/plugins/ai-assistant-plugin/components/seo-enhancer/store/selectors.ts	0/12 (0.00%)	0.00%	1 ❤️‍🩹

Full summary · PHP report · JS report

[CGastrell]

This works perfectly, thanks @coder-karen