Feature/bf 2025 c

[enricobattocchi]

Context

• We want to prepare the 25.9 release by merging the feature branch feature/bf-2025 to trunk.

Summary

This PR can be summarized in the following changelog entry:

• Updates the Black Friday ads.

Relevant technical choices:

• This PR combines the following individual PRs:
  • fix BF ad margin on elementor #22531
  • 750 black friday ads 2025 update ads in editor #22530
  • Set correct timing. #22524
  • 749 adapt ads for new pricing and packaging update feature modal upsells in editor #22523
  • Add images for BF modals #22519
  • Render black friday sale label. #22517
  • 751 black friday ads 2025 plans page #22512
  • Add the Black Friday announcement modal #22507
  • fix notification copy and BF badge #22504
  • Update styling for the black friday ads. #22497

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 editors:
  • With and without the BF promotion active
    • When the BF promotion is active, test with and without WooCommerce active

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.

Impact check

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

• N/A

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.

Fixes #

[enricobattocchi]

Tests are failing because of the coveralls upload, merging