#7659366 Update/modify renewal paths

Proposed Changes

• This PR modifies the cancellation flow paths for Jetpack products so that product cancellation uses the main cancellation flow instead of the auto-renew on/off toggle.
• This PR also modifies the appearance of the “Renew now” button that shows on individual purchase pages so that is shows in the chosen theme’s primary color.
• This PR also adds some additional language to the purchase cancellation screen when a purchase is within the refund window.

Context: p1HpG7-j9Q-p2

Testing Instructions

• To test, you will need a Jetpack site with a purchased Jetpack plan/ product. Note that you should not use a purchase made with credits as the test instructions will not work properly.

• Check out this branch in your testing environment.

• Navigate to /me/purchases and select your Jetpack purchase from the list.

• On the purchase page, if automatic renewal is ON, the “Subscription Renewal” section of the purchase page will just show the next renewal date and no auto-renew on/off toggle.
  

• On the purchase page, if automatic renewal is OFF, the “Subscription Renewal” section of the purchase page will show the expiration date of the subscription and provide a link to Re-enable automatic renewal.
  

• Click on the “Re-enable” link and confirm that the text that the “Subscription Renewal” section changes from showing an expiry date to showing the next renewal date and that the “Re-enable” link goes away.

• Note that on the purchase page, the “Renew Now” button shows in the chosen theme’s primary color.
  

• Click on the “Cancel Subscription” button at the bottom of the Purchase page to go to the Cancel Purchase page.
  

• If your purchase is still within the refund window (which will be true if you made a new purchase for this test), you should see some updated copy on the cancel purchase page:
  

• These changes should be restricted to Jetpack purchases only. Test with a WordPress.com plan to confirm that the auto-renew on/off toggle still shows for this purchase.

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 and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?