Sites Dashboard: Update action's isEligible checks to exclude Jetpack/P2 sites from the action options

[lsl]

Fixes https://github.com/Automattic/dotcom-forge/issues/9971

Proposed Changes

The Jetpack action items were lost when merging https://github.com/Automattic/wp-calypso/pull/94238/files?w=1#diff-173bec7d847197dc6a90c47661016102ba95728dab618e17b774c11c7ed1994cL550-L565, this PR adds these actions and the migration related ones back into the list. It also hides the wpcom site actions that aren't relevant to Jetpack/p2 sites.

Testing Instructions

• non-Atomic Jetpack sites
  • Create a site with jurassic
  • Connect your WP.com account through Jetpack
  • Observe your site is listed on /sites
  • Observe 'Jetpack Cloud', 'Billing', 'Support', 'Migrate to WordPress.com' actions are shown.
  • 
• non-Atomic sites added via A4A plugin
  • Go to https://agencies.automattic.com/sites
  • Click "Add sites" > "Via the Automattic plugin" and enter your site's URL
  • Install and activate A4A plugin on your site
  • Connect your site
  • Observe your site is listed on https://wordpress.com/sites
  • Observe 'Migrate to WordPress.com' actions are shown.
  • 
  • I was unsure how to create a Jetpack disconnected non-Atomic site. The original code and the comment suggests Sites connected through A4A plugin are listed on wordpress.com/sites even when Jetpack is deactivated, but when you connect a site through A4A plugin, Jetpack gets connected automatically. If you disconnect Jetapck afterward, the site no longer appear on wp.com/sites anymore.
• P2 sites
  • Observe some actions are hidden (See sites-dataviews-actions.test.ts).
• Observe no regressions for Simple sites and Atomic sites

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-125888&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~427 bytes added 📈 [gzipped])

name                parsed_size           gzip_size
staging-site            +2101 B  (+0.1%)     +427 B  (+0.1%)
sites-dashboard         +2101 B  (+0.2%)     +427 B  (+0.1%)
site-tools              +2101 B  (+0.1%)     +427 B  (+0.1%)
site-settings           +2101 B  (+0.1%)     +427 B  (+0.1%)
site-performance        +2101 B  (+0.1%)     +427 B  (+0.1%)
site-overview           +2101 B  (+0.1%)     +427 B  (+0.1%)
site-monitoring         +2101 B  (+0.2%)     +427 B  (+0.1%)
site-marketing          +2101 B  (+0.1%)     +427 B  (+0.1%)
site-logs               +2101 B  (+0.2%)     +427 B  (+0.1%)
hosting-features        +2101 B  (+0.2%)     +427 B  (+0.1%)
hosting                 +2101 B  (+0.1%)     +427 B  (+0.1%)
github-deployments      +2101 B  (+0.1%)     +427 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/jetpack-actions on your sandbox.

[lsl]

I was unsure how to create a Jetpack disconnected non-Atomic site. The original code and the comment suggests Sites connected through A4A plugin are listed on wordpress.com/sites even when Jetpack is deactivated, but when you connect a site through A4A plugin, Jetpack gets connected automatically. If you disconnect Jetapck afterward, the site no longer appear on wp.com/sites anymore.

This required creating the site via pressable and deactivating Jetpack + Jetpack protect while still having the A4A client plugin installed (the a4a client plugin maintains a Jetpack connection irrc).

All the hosting options are hidden, only open/wpadmin/move links are present:

[lsl]

P2:

Self hosted JP:

Simple sites:

Atomic:

Staging: