Add/bundles to recommendations

[CodeyGuyDylan]

Proposed changes:

• Add product cards for bundles (Security, Complete, and Growth)
• Add interstitials for bundles
• Add complete class to enable interstitial and product card for it
• Fix issue with ineligible intro-discounts showing on recommendation cards

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

P2: pbNhbs-bxX-p2

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

No

Testing instructions:

1. Checkout this branch via the Jetpack Beta plugin or your local dev environment
2. Make sure your JN site has access to your sandbox
3. Enable your sandbox on your testing site
4. Checkout the following diff on your sandbox: D166839-code
5. Go to My Jetpack and fill out the welcome banner survey and check all possible options so you can see Jetpack Complete
6. Ensure you see the Jetpack Complete recommendation. Make sure the "Purchase" button goes to checkout with Complete in the cart
7. Click on "Learn More" to see the new Complete interstitial. Make sure the interstitial works correctly by testing the CTA and ensuring it goes to checkout with Complete in the cart.
8. Go back to My Jetpack and redo the recommendation survey. This time select Protect my site only. This should ensure you see the Security card. Test the same things you did with Complete with the interstitial and the card itself
9. Go back to My Jetpack one more time and redo the survey again. This time, select only Grow my audience. Test this the same way you tested the last two bundles
10. You've now tested all the new interstitials and recommendation cards. Now go to /wp-admin/admin.php?page=my-jetpack#/add-social and ensure that the bundle upsells still look like they used to and should
11. Lastly, we'll test the intro discount eligibility on the cards. Purchase any plan that you see in your recommendations on the site. For this example, I'll use Protect.
12. After purchasing protect go remove it from your site via wordpress.com/me/purchases or the Store Admin
13. Go back to My Jetpack and ensure you no longer see the intro discount on the card

[github-actions[bot]]

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/bundles-to-recommendations branch.

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

  bin/jetpack-downloader test jetpack add/bundles-to-recommendations

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[bot]]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• :white_check_mark: Include a description of your PR changes.
  
• :white_check_mark: Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• :white_check_mark: Add testing instructions.
  
• :white_check_mark: Specify whether this PR includes any changes to data or privacy.
  
• :white_check_mark: 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 :robot:

---

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!