Revert 69331: ETK deactivation message on unlaunched site

[samiff]

Proposed Changes

Follow-up to #69331
Closes #79804

This reverts commit e67ae55.

As the coming-soon functionality has now been moved to the jetpack-mu-wpcom package which is utilized in wpcomsh for WoA sites.

Testing Instructions

• When deactivating the updated ETK plugin, there should no longer be the "Disabling this plugin will make your site public" message displayed.
• Coming Soon functionality should otherwise remain unchanged.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-75120

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-75120&env=jetpack

[matticbot]

This PR modifies the release build for editing-toolkit

To test your changes on WordPress.com, run install-plugin.sh editing-toolkit revert/69331-etk-deactivation-message on your sandbox.

To deploy your changes after merging, see the documentation: PCYsg-mMA-p2

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[miksansegundo]

LGTM 👍 Thanks!