#7931307 Domains: Adapt domain registrant verification page to be used with DSAPI reseller domains

Proposed Changes

This PR updates the domain registrant verification landing page (/domain-services/registrant-verification/) to be used with DSAPI reseller domains.

A new reseller=reseller-name query parameter can be added to the URL. When that’s added, references to WPCOM links and support pages are removed. If the reseller is tumblr, the Tumblr logo is shown in place of the WordPress logo.

Screenshots

• Success

• Email already verified

• Expired email

• Mismatched email address

• Error message

Testing Instructions

• Open the live Calypso link or build this branch locally
• Hack your backend’s /domains/{domain}/verify-email endpoint to return different success and error responses
• Access the registrant verification landing page with some example query parameters, e.g. /domain-services/registrant-verification?domain=example.com&email=example@example.com&token=1234&reseller=tumblr_ote
• Ensure the different backend responses’ show pages as shown in the screenshots above

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• 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)?