My Jetpack: Remove "Connection" management section for Atomic sites.

[elliottprogrammer]

This PR removes the "Connection" status & management section in My Jetpack for Atomic sites.

Jetpack should always be Active on WoA sites and users should not be able or allowed to manually "disconnect" their Jetpack connection. Therefore, the "Connection" section in My Jetpack is not needed and not wanted on WoA sites because it may cause user confusion and possibly invite and allow users to disconnect their Jetpack connection on their Atomic site. Removing the "Connection" section for WoA sites will prevent users from manually disconnecting their site.

P2 post & discussion: pf5801-1d5-p2

Fixes https://github.com/Automattic/jetpack-marketing/issues/1078

Proposed changes:

• Don't render component if site isAtomic.

Other information:

• [ ] Have you written new tests for your changes, if applicable?
• [ ] Have you checked the E2E test CI results, and verified that your changes do not break them?
• [ ] Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

pf5801-1d5-p2

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

Testing instructions:

Prerequisite:

• You'll need a WordPress on Atomic (WoA) site to test this PR.
• If you don't already have one, you can create a WoA site via the WoA Developer Blog Manager in MC (/atomic/wpcom-dev-blogs/)

Instructions:

• Ensure you are using the WP-Admin interface to manage your site:
  • Go to Settings --> General --> Admin interface style --> Classic style (then click "Save").
• Open the My Jetpack page, notice that there is a "Connection" section on the bottom-right corner of the page. Notice that this section allows the user to "Manage" the connection (and disconnect). We don't wan't to allow this on Atomic (WoA) sites.
• Upload and install & activate the latest version of the Jetpack Beta Tester plugin.
• Open Jetpack Beta, select the Jetpack plugin, and enable the update/my-jetpack-atomic-remove-connection branch.
• Open the My Jetpack page.
• Verify that the "Connection" section is not showing or available (See Screenshot ⤵️):

Screenshot:

[github-actions[bot]]

Thank you for your PR!

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

• :white_check_mark: Include a description of your PR changes.
  
• :white_check_mark: Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• :white_check_mark: Add testing instructions.
  
• :white_check_mark: Specify whether this PR includes any changes to data or privacy.
  
• :white_check_mark: 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 :robot:

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions[bot]]

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 WordPress.com Simple 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, and enable the update/my-jetpack-atomic-remove-connection branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/my-jetpack-atomic-remove-connection

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