Hide upgrade menu item on multisite installs

[CGastrell]

Proposed changes

• Hide the "Upgrade Jetpack" sidebar menu item on multisite installations. The upsell is not relevant in multisite environments where plan management is handled at the network level.

Discussion

p1775143980027909-slack-CDLH4C1UZ

Other information

• Generate changelog entries for this PR (using AI).

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

No.

Testing instructions

• Set up a multisite environment
• Verify the "Upgrade Jetpack" menu item does not appear in the sidebar
• On a single-site install with a free plan, verify the menu item still appears as expected

🤖 Generated with Claude Code

[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 or WordPress.com Site Helper), and enable the fix/hide-upgrade-menu-multisite branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/hide-upgrade-menu-multisite

bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix/hide-upgrade-menu-multisite

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/admin-ui/src/class-admin-menu.php	99/124 (79.84%)	-0.49%	1 ❤️‍🩹

Full summary · PHP report · JS report

_{Coverage check overridden by Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR .}

[CGastrell]

Turn to draft, we're keeping current behavior for now: p1775153795475889/1775143980.027909-slack-CDLH4C1UZ