Privacy: Return before scheduling cron during install to avoid error.

r43046 introduced `wp_schedule_delete_old_privacy_export_files()` to schedule the `wp_privacy_delete_old_export_files` cron job, but it did not check to make sure it wasn't running in the context of the install process. When it did run in that context, it created a database error, because the necessary database tables don't exist at that point.

Checking the current context and returning early during the installation phase avoids that issue.

Props helen, timothyblynjacobs, iandunn.
Fixes #43952.

Built from https://develop.svn.wordpress.org/trunk@43162


git-svn-id: http://core.svn.wordpress.org/trunk@42991 1a063a9b-81f0-0310-95a4-ce76da25c4cd

wp-includes/functions.php

@@ -6264,6 +6264,10 @@ function _wp_privacy_active_plugins_change() {
  * @since 4.9.6
  */
 function wp_schedule_delete_old_privacy_export_files() {
+	if ( wp_installing() ) {
+		return;
+	}
+
 	if ( ! wp_next_scheduled( 'wp_privacy_delete_old_export_files' ) ) {
 		wp_schedule_event( time(), 'hourly', 'wp_privacy_delete_old_export_files' );
 	}

wp-includes/version.php

@@ -4,7 +4,7 @@
  *
  * @global string $wp_version
  */
-$wp_version = '5.0-alpha-43160';
+$wp_version = '5.0-alpha-43162';
 
 /**
  * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.