My Jetpack: add post-activation experiment

[IanRamosC]

Proposed changes:

Implemented 2 different welcome flow experiences:

Control: After user connects the site, they are presented with a survey asking what their site goals are. Upon submission of the survey, the user given product recommendations based on their site goals.
Treatment: After the site is connect, they'll be redirected to the pricing page immediately.

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 /wp-admin/options-general.php?page=companion_settings and point JETPACK__SANDBOX_DOMAIN to your sandbox
• Visit the experiment page on 22057-explat-experiment, go to the Audience section on the experiment overview page and hover the “Bookmarklet” link of treatment.
• Make sure your sandbox has the most recent trunk
• Go back to My Jetpack and click on "Activate Jetpack with on click"
• After your site is connected, you'll be redirected to the pricing page
• If you complete a purchase, you'll be redirected to My Jetpack after you connect your site and the license is attached

[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!

[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/my-jetpack-pricing-page-experiment branch.

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

  bin/jetpack-downloader test jetpack add/my-jetpack-pricing-page-experiment
  

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

[CodeyGuyDylan]

Other than the issue with the "Start for free" button on the pricing page, this looks good! Approving as that seems like it is a Calypso issue.

For the sake of public info, when directed to the pricing page in the context of this experiment, the "Start for free" button is going to the https://cloud.jetpack.com/pricing/jetpack-free/welcome URL rather than directing back to My Jetpack

[IanRamosC]

For the sake of public info, when directed to the pricing page in the context of this experiment, the "Start for free" button is going to the https://cloud.jetpack.com/pricing/jetpack-free/welcome URL rather than directing back to My Jetpack

Got a fix for that here, since this is a new flow.