Plans in site creation: Plan selection screen

[ravishanker]

Fixes #19284

Domains	Plans (to be updated)

To test:

Note
Waiting for Automattic/wp-calypso#82135

• Launch JP app
• Go to Me-> Debug settings
• Switch to Remote Feature tab, find plans_in_site_creation and enable it
• Switch to My Site tab
• Tap the down arrow to the right of the site name on the My Site screen
• Tap the + icon at the top right on the Site picker screen
• Select ⊕ Create WordPress.com site on the modal dialog
• Tap Skip at top right on the first step (topic screen)
• Tap Skip at top right on the next step (theme screen)
• Enter a search query (whatever you want here)
• Verify that result domains are as shown in the screenshot above
• Select a domain
• Verify Plans screen opens with Personal, Premium, Business, and Ecommerce plans
• Select a plan
• Verify it return to site setup screen
• Verify it opens checkout, after site setup when an annual paid plan is chosen
• Verify it doesn't open checkout if a free domain with free plan is chosen, and site setup is completed
• Verify it doesn't allow a annual plan to be selected with a free domain
• Also, Verify, select a paid domain on the previous step, then choose to continue with a free domain, free plan

Checkout

• Setup sandbox cookie to test checkout (see instructions on Test Plan)
• Complete checkout with a paid domain, and paid annual plan

Regression Notes

1. Potential unintended areas of impact
   N/A

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   Tested various flows

3. What automated tests I added (or what prevented me from doing so)
   Existing unit tests

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr19304-05d9682
	Commit	05d9682
	Direct Download	jetpack-prototype-build-pr19304-05d9682.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr19304-05d9682
	Commit	05d9682
	Direct Download	wordpress-prototype-build-pr19304-05d9682.apk

Note: Google Login is not supported on these builds.

[staskus]

@ravishanker could you mention the steps to make in the code so I could test with a current Calypso build? Or maybe you have some feedback about the Calypso build to determine if we're good to merge it or if something is still missing?

[peril-wordpress-mobile]

	Warnings
⚠️	This PR is assigned to a milestone which is closing in less than 4 days Please, make sure to get it merged by then or assign it to a later expiring milestone
⚠️	PR has more than 300 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS

[ravishanker]

@ravishanker could you mention the steps to make in the code so I could test with a current Calypso build? Or maybe you have some feedback about the Calypso build to determine if we're good to merge it or if something is still missing?

Probably, better to test it after merging the Calypso PR. It needs to login on Calypso, and doesn't seem to work with Calypso.live url at the moment.

[irfano]

Great job on adding plans and connecting all these steps. 👏🏻
🟡 Creating a free site and a free domain doesn't work as expected. It creates a site with a domain that was not selected.
🟢 I successfully purchased a domain and a plan with a fake purchase.
🟢 No network error screens in site setup and plan section displayed.
🟢 The retry button on the network error screens in the site setup and plan section worked.
🟢 Tapping the back button in various steps in the flow worked as expected.

I've addressed the 🟡 issue in another PR. Also, I haven't included my minor comments here; instead, I've added them to that PR: #19377