Add support for autoloading enhancements in WordPress 6.6 trunk to autoloaded options Site Health check

[felixarntz]

Summary

This PR fixes the test failures seen in https://github.com/WordPress/performance/actions/runs/8547642712/job/23420147133?pr=1111, which are unrelated to the PR they're reported on. The next time we'll make a PHP change against trunk, we should see the same failures too.

Relevant technical choices

The failures happen due to https://core.trac.wordpress.org/changeset/57920 which makes an intentional change regarding large autoloaded options, to no longer autoload them unless $autoload = true is explicitly provided. Additionally, there are now more database values than yes that should trigger autoloading. All of this is expected. Plugins that perform low-level optimizations around autoloaded options are likely to run into similar failures - all of which is straightforward to fix though. This is why the underlying Trac ticket is annotated with needs-dev-note.

So we need to do two things:

• In the production code, update our low-level database queries to take into account the new values that should result in options being autoloaded, via the new core function wp_autoload_values_to_autoload() that exists for this purpose.
• In the tests, explicitly force the excessively large options in the tests to be autoloaded, otherwise they obviously won't get picked up as autoloaded options.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: thelovekesh <thelovekesh@git.wordpress.org>
Co-authored-by: felixarntz <flixos90@git.wordpress.org>
Co-authored-by: mukeshpanchal27 <mukesh27@git.wordpress.org>
Co-authored-by: joemcgill <joemcgill@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[felixarntz]

Once this fix is merged into release/3.0.0, we should also merge it into trunk to avoid failures in that branch.

[mukeshpanchal27]

Overall look good to me. Left some nit-pick

[joemcgill]

Just one suggestion but not a blocker.

[joemcgill]

Rather than repeating this several times, how about consolidating it to our own perflab_aao_get_autoload_values() helper?

[felixarntz]

@joemcgill Great idea, done in 0316586