Merges the feature branch feature/fix-assessments into trunk

[mhkuu]

Context

• We want to prepare the 23.2 release by merging the feature branch feature/fix-assessments to trunk.

Summary

This PR can be summarized in the following changelog entry:

• Merges the feature branch feature/fix-assessments into trunk.

Relevant technical choices:

This PR combines the following individual PRs:

• Enhancements:
  • Adds "Optimize with AI" buttons next to SEO assessments #21348
  • Excludes keyphrases from complex words #21400
  • Excludes image captions from keyphrase in introduction assessment #21414
• Non-user-facing:
  • Updates the styling of the AI buttons #21415
  • Adds AI Optimize upsell introduction modal #21417
  • Disables all AI buttons other than the one currently in use #21418
  • Prevents showing the AI buttons in the Elementor in-between page #21420
  • Allows adding additional CSS classes to the Toast's close button #21423
  • Updates the copy for the introduction and consent modals #21431
  • Prevents showing AI buttons for scenarios we don't cover #21436
  • Fixes showing of tooltip on AI buttons #21437
  • Fixes AI buttons in the sidebar going blank after closing the metabox #21439
  • Changes 'blue' to 'indigo' in all AI components #21441
  • Disables the AI buttons when the editor or blocks are in HTML mode #21443
  • Refactors the SparklesIcon for reusability #21449
  • Adds lock icon to AI buttons #21450
  • Updates copy on the new AI features in the card and the upsell #21452
  • Makes "Yoast AI" non-translatable in the feature card #21454
  • Allows disabling individual AI buttons #21457
  • Deprecates old AI introduction and fixes deprecation messages #21465
  • Fixes degraded performance of content analysis #21474

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Smoke the the AI Optimize functionality.

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 (Default Block/Gutenberg/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. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

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.

[github-actions]

@mhkuu Please be aware that following packages have been abandoned and are not actively maintained anymore:

Package name	Path
@yoast/babel-preset	packages/babel-preset
@yoast/components	packages/components
@yoast/e2e-tests	packages/e2e-tests
@yoast/helpers	packages/helpers
@yoast/jest-preset	packages/jest-preset
@yoast/style-guide	packages/style-guide

Please consider using the other packages instead.

[mhkuu]

Not sure why this icon is loaded as an SVG 🤔 See #21450 -- I've created #21482 to check this.

[mhkuu]

Do we need to add this deprecation as an "other" changelog? See #21465.

[mhkuu]

#21418 seems to have been removed in #21415 -- this needs to be re-applied. Issue created: #21481.