Revert: Enable RTC by default

[chriszarate]

Revert the changes that enabled RTC by default for WP 7.0 Beta 1 per this comment.

• This preserves the unit tests for WP_REST_Autosaves_Controller; they pass whether the feature is enabled or not.
• Since the REST API endpoints are conditionally registered, the QUnit fixtures must be updated.

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

[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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props czarate, paulkevan.

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

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[pkevan]

We'll need to bump $wp_db_version again once this lands.

[github-actions]

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 61702
GitHub commit: 702af38

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

[ellatrix]

We'll need to bump $wp_db_version again once this lands.

@pkevan Do we? We already did a bump that will have caused the option to be populated. Once it's populated, a further bump will not do anything? Those who triggered the DB upgrade will have it enabled by default, but they can turn it off in settings. Those who hadn't upgraded yet will get it disabled by default? Or is this incorrect?

[pkevan]

We'll need to bump $wp_db_version again once this lands.

@pkevan Do we? We already did a bump that will have caused the option to be populated. Once it's populated, a further bump will not do anything? Those who triggered the DB upgrade will have it enabled by default, but they can turn it off in settings. Those who hadn't upgraded yet will get it disabled by default? Or is this incorrect?

yeah I was confused - ignore me 😄