Options: Update default autoload values used in core

[joemcgill]

Following r57920, WordPress will now use one of 'on', 'off', 'auto-on', 'auto-off', or 'auto' for the autoload value stored in the DB, while still supporting the previous 'yes' and 'no' values for backwards compatibility.

However, there are still many places in core that will create new options using the previous values. These should be updated to use the new schema for consistency.

Most notably, populate_options() sets options on a new site using the previous 'yes' or 'no' values.

Other functions to update:

• set_transient()
• add_network_option()
• wp_ajax_wp_compression_test()

There may be others that I missed in a quick scan of the codebase, but those should cover most cases.

Updated values of 'autoload' option from 'yes' or 'no' to 'on' or 'off' respectively, across several PHP files. This change was implemented in the functions handling options and lock settings, enhancing clarity and consistency of the code.

[joemcgill]

I have reviewed ​PR #6417 and am marking for commit. I'll handle unless someone beats me to it or additional feedback is raised.

[joemcgill]

A couple of small revisions are needed. Removing the commit keyword.

[joemcgill]

In 58105:

Options: Update default autoload values used in core.

This updates the values used for the $autoload parameter in various functions to replace 'yes' and 'no' with 'on' and 'off', respectively.

Follow-up to [57920].

Props pbearne, mukesh27, joemcgill.
Fixes #61045. See #42441.

Merged in https://core.trac.wordpress.org/changeset/58105.

[joemcgill]

Reopening this because I just realized that [58105] confused the stored database values 'on'/'off' with the parameter values true/false for add|update_option().

This fixes some instances of autoload values changed in r58105 where the database values of 'on' or 'off' were passed to option functions rather than the supported values of true or false.

Trac ticket: https://core.trac.wordpress.org/ticket/61045

@joemcgill Should we change the one at schema.php as well?
​https://github.com/WordPress/wordpress-develop/blob/459d99618c4dd6d412d7ad5a5d96e79e87602dc6/src/wp-admin/includes/schema.php#L599

@Rajinsharwar

Should we change the one at schema.php as well?

No, I don't think so. There were many cases like this one in the original commit that were updating values directly in the DB via direct queries, rather than through the add|update_option() functions. Those cases should be using "on" and "off".

[joemcgill]

In 58416:

Options: Fix some default autoload values used in core.

This fixes some autoload values that were updated in [58105] that used the database values of "on" and "off" instead of the boolean values true and false when being passed to add|update_option().

Props joemcgill, desrosj, rajinsharwar.
Fixes #61045. See #42441.

Committed in https://core.trac.wordpress.org/changeset/58416