Flush dynamically scheduled core cron events in Behat tests

[swissspidy]

Description

In WordPress 6.3.0+, WordPress core introduced the wp_delete_temp_updater_backups cron hook. This hook is dynamically scheduled for time() (now) when WP_Upgrader is first instantiated on a site (which occurs when wp_version_check executes and finds update/translation offers from api.wordpress.org).

During wp cron event run --all on fresh installs, wp_delete_temp_updater_backups is scheduled mid-execution and is not included in the initial snapshot of events executed by run --all. As a result, it remains queued as due now, causing subsequent wp cron event run --due-now assertions in Behat tests to fail when they expect 0 due events.

This PR adds a wp cron event run --due-now step to flush any dynamically scheduled core cron events before asserting 0 due events.

This makes the tests more resilient as they were temporarily failing because wp-cli/wp-cli-tests#337 wasn't merged yet after the most recent minor release.

Summary by CodeRabbit

• Bug Fixes
  • Updated cron event execution messaging to reflect newer WordPress behavior.
  • Improved validation of --due-now results by accepting successful execution totals instead of requiring an exact zero-event message.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!