Merges the feature branch feature/ai-optimize-classic to trunk

[mhkuu]

Context

• We want to prepare the 25.2 release by merging the feature branch feature/ai-optimize-classic to trunk.

Summary

This PR can be summarized in the following changelog entry:

• Merges the feature branch feature/ai-optimize-classic into trunk.

Relevant technical choices:

This PR combines the following individual PRs:

• Non-user-facing.
  • Adds an upsell for AI Optimize on products #22254
  • Enable AI optimize in Classic editor #22118
  • Disable AI Optimize button in taxonomies #22246
  • Add in app notifications for classic editor #22223

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Smoke test the AI Optimize functionality, specifically for the Classic Editor.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Block/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• See the individual PRs.

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

• I have written documentation for this change.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

[coveralls]

Pull Request Test Coverage Report for Build 15936d2b846c322fa3b4b91e32ba3f7c002a45a6

Details

• 37 of 68 (54.41%) changed or added relevant lines in 11 files are covered.
• 3 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.06%) to 58.702%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/js/src/ai-optimizer/components/ai-optimize-button.js	23	24	95.83%
packages/js/src/introductions/components/provider.js	0	1	0.0%
packages/js/src/introductions/initialize.js	0	1	0.0%
packages/js/src/components/contentAnalysis/ReadabilityAnalysis.js	0	4	0.0%
packages/js/src/components/contentAnalysis/SeoAnalysis.js	0	4	0.0%
packages/js/src/ai-optimizer/components/modal-content.js	0	6	0.0%
packages/js/src/ai-generator/components/modal-content.js	2	16	12.5%

Files with Coverage Reduction	New Missed Lines	%
packages/js/src/components/contentAnalysis/SeoAnalysis.js	1	0.0%
packages/js/src/components/contentAnalysis/ReadabilityAnalysis.js	2	0.0%

Totals
Change from base Build 47efeb585d6caa332bb2e3408a011ad5177707d9:	0.06%
Covered Lines:	14070
Relevant Lines:	23664

---

💛 - Coveralls