My Jetpack: add feature as possible recommendations

[IanRamosC]

Proposed changes:

• This PR updates the frontend of My Jetpack in order to display feature modules as possible recommendations. The product cards were adapted to handle feature and their various statuses.

NOTE: the new feature cards work similar to how the product cards work. There's an issue where the state isn't immediately reflected when we, for example, activate a module. That behavior should be fixed in a follow-up.

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

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

Testing instructions:

• Spin up a JN site with Jetpack Beta pointing to this branch and enable sandbox access
• Go to Jetpack Constants and update JETPACK__SANDBOX_DOMAIN to your sandbox domain
• Checkout this branch in your sandbox: 168603-ghe-Automattic/wpcom
• Connect My Jetpack, and wait until you see the recommendations survey
• Check "Grow my site" and wait until you see the recommendations
• Confirm that you can see and interact with "Related Posts" and "Newsletter"

[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 add/feature-recommendations-cards branch.

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

  bin/jetpack-downloader test jetpack add/feature-recommendations-cards
  

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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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!

[robertsreberski]

Thanks for working on that functionality, it works good and seems reliable. I am aware it was not easy to combine free features and products.

I do see the state of the product updating, it just has a long delay 🤔 Anyways, I agree with leaving it out of scope of this PR, and resolve it in the follow up task.