ThreatsDataViews: Update isPrimary actions

[dkmyta]

Description #
Moves access to actions toggles inline and hides the collapsible actions list

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

• https://github.com/Automattic/jetpack-scan-team/issues/1472

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

• No

Testing instructions:

• Checkout this branch
• Load storybook with cd projects/js-packages/storybook && npm run storybook:dev
• View the Threats Data View component
• Ensure the content of the actions section is positioned and styled according to designs in both Table and List views
• Review the code and ensure the implementation is correct

Screenshots

Table View:

List View:

[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 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/components/threats-data-view-actions branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

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

  bin/jetpack-downloader test jetpack update/components/threats-data-view-actions
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/components/threats-data-view-actions
  

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 Team 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 🤖

---

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!

---

Protect plugin:

• Next scheduled release: none scheduled.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[nateweller]

Do we compensate for this with other focus styles?

[dkmyta]

We do not - I wasn't quite sure to what extent we should compensate for all these things directly within the component or whether various parts should be handled in the implementation.

I removed the built in button element pseudo-class styles here and set the internal span element, text styles and a hover effect to match the colours in the designs, but there are other pieces in the component where we default to wp-admin style settings. Should we account for all of this here, or should we allow for the default and update everything where it's in use?

[dkmyta]

Closing in favour of adding the primary fixer actions to a dedicated column and keeping secondary action in the collapsible list as proposed in #39754.