Queue async transitions for posts force-published by Cron Control

[ethitter]

trafficstars

Cron Control includes a job that runs every minute, force-publishing posts that missed their scheduled times. Since the async transitions code excludes the CLI context (#471), this manually queues the events.

[WPprodigy]

Maybe needs adjustments post-https://github.com/Automattic/vip-go-mu-plugins/pull/1999.

Of note, there's a good possibility of this module being deprecated and moved away from.

[WPprodigy]

Confirming that we will be deprecating/removing the async publish posts module very soon.

Going to leave this PR open for a little in case I'll be migrating the plugin to an individual customer-repo where this code would be profitable.

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[codecov[bot]]

Codecov Report

Merging #762 (a706066) into develop (e995314) will increase coverage by 0.00%. The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             develop     #762   +/-   ##
==========================================
  Coverage      33.23%   33.23%           
  Complexity      3491     3491           
==========================================
  Files            216      216           
  Lines          13739    13742    +3     
==========================================
+ Hits            4566     4567    +1     
- Misses          9173     9175    +2     

Impacted Files	Coverage Δ
001-cron.php	0.00% <0.00%> (ø)
vip-mail.php	60.00% <0.00%> (-2.86%)	:arrow_down:
security/class-lockout.php	55.55% <0.00%> (+1.85%)	:arrow_up:
lib/statsd/class-statsd.php	31.37% <0.00%> (+3.92%)	:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[github-actions[bot]]

This pull request has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.

This is an automation to keep pull requests manageable and actionable and is not a comment on the quality of this pull request nor on the work done so far. Closed PRs are still valuable to the project and their branches are preserved.