#7583345 Update Jetpack Cancellation form input

Proposed Changes

• Add new answer for cancellation form: “I no longer need a website”
• Add optional text field to all answers of the form
• Make “Other” text field required so they have to fill out a reason before cancelling

Discussion

P2s:
p1HpG7-hcM-p2
p1HpG7-hzP-p2
pbNhbs-3MF-p2

Asana:
1161179020265237-as-1202940054684628/f

Testing Instructions

1. Checkout this branch via git switch update/jetpack-cancellation-form-input
2. Purchase any Jetpack plan on whichever site you would like.
3. Start Jetpack Cloud via yarn start-jetpack-cloud
4. Go to http://jetpack.cloud.localhost:3000/purchases/subscriptions/{site}
5. Select a subscription and then select “Remove Subscription”
   
6. Select “Next Step”
   
7. Go through and select all of the answers, and notice the optional text field that shows up underneath them. Also notice the “Remove Subscription” button is NOT disabled or greyed out. Also notice the new “I no longer need a website” answer
   
8. Select “Other” and notice the different wording and the “(required)” indicator
   
9. With “Other” selected and the text box empty, notice that the “Remove Subscription” button is greyed out and disabled
   
10. Type some text into the “Other” text field and notice the “Remove Subscription” button become enabled and its regular color
    
11. Test the survey on mobile and desktop to make sure the layout looks good in all widths.
12. Next, cancel the jetpack cloud local environment and start regular calypso via yarn start
13. Navigate to http://calypso.localhost:3000/me/purchases/{site}/
14. Repeat steps 5-11 on this page to test out Calypso Blue. The behavior should be exactly the same except the “Remove Subscription” button will stay “Next Step” instead
    

Pre-merge Checklist

• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and [Using memoizing selectors](https://react-redux.js.org/api/hooks#using-memoizing-spproach to Data](https://github.com/Automattic/wp-calypso/blob/trunk/docs/our-approach-to-data.md)
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?