RTC: Re-enable RTC by default on WoW sites

[mmtr]

Fixes DOTCOM-17053

Proposed changes

• Reverts the temporary IS_ATOMIC early-return added in RTC: Temporarily disable default on WoW sites #48199 to Automattic\Jetpack\RTC\RTC::default_rtc_option(), so RTC is enabled by default again on WoW (Atomic) sites.
• The CRDT-document bug that motivated RTC: Temporarily disable default on WoW sites #48199 was fixed upstream in WordPress/gutenberg#77529, shipped in Gutenberg 23.0, which has already been deployed to Atomic sites.
• Drops the unreleased dotcom-16781-temporarily-disable-rtc-on-atomic-sites changelog entry (the temp-disable hadn't been released at the package level yet — last rtc package release is 0.1.0) and adds a new changed entry covering the re-enable.

Related product discussion/links

• Original temp-disable: RTC: Temporarily disable default on WoW sites #48199 / DOTCOM-16781
• Upstream fix: RTC: Fixed orphaned meta causing dirty editor state WordPress/gutenberg#77529

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• Apply these changes to a WoW (Atomic) site that has never explicitly toggled the RTC setting (i.e. the wp_collaboration_enabled / wp_enable_real_time_collaboration option is not stored in the DB).
• Go to Settings → Writing.
• The "Enable real-time collaboration" toggle should now default to enabled.
• Confirm RTC works as expected in the editor with another user, and that the editor does not get stuck in a permanently dirty state (the bug fixed by gutenberg#77529).

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the dotcom-17053-re-enable-rtc-by-default-on-wow-sites branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack-mu-wpcom-plugin dotcom-17053-re-enable-rtc-by-default-on-wow-sites

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/rtc/src/class-rtc.php	131/158 (82.91%)	0.41%	-1 💚

Full summary · PHP report