Social: remove support section from admin page

[dhasilva]

Fixes #

Proposed changes

• Removes the support section (help/docs links) from the Jetpack Social admin page: we generally use My Jetpack → Help route for support. My Jetpack is available for both Jetpack and standalone plugins.
• Deletes the support-section/ component and its IconText helper + styles.
• Cleans up the now-unused import in admin-page/index.tsx.

Related product discussion/links

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

No.

Testing instructions

• Build the Social plugin: jetpack build plugins/social --deps
• Activate Jetpack Social on a site, connect it, and visit Jetpack → Social.
• Confirm the "Need help?" / support section no longer appears at the bottom of the dashboard.
• Confirm the rest of the admin page (header, toggles, pricing page for free sites, info section, footer) still renders normally.
• Local test runs on this branch:
  • JS unit tests in projects/packages/publicize: 46 suites / 337 tests passed.
  • Social Playwright e2e (admin-page.test.ts, connection.test.ts, social-sidebar.test.ts): all passed.

[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 (Jetpack), and enable the update/social-remove-support-section branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/social-remove-support-section

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!

[simison]

FYI @Automattic/triforce @keoshi , removint the seection/designs approved by @ilonagl

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[CGastrell]

LGTM!