Domains: Replace Nominet-specific verification with generic custom_verifications

[hambai]

Proposed Changes

• Replace the nominet_pending_contact_verification_request and nominet_domain_suspended boolean API properties with a single custom_verifications: string[] array across all domain type definitions, assemblers, and the Redux schema.
• Add a verification_type parameter to the domain contact verification API mutation so the backend can distinguish between different verification workflows.
• Refactor the Dashboard domain contact verification page to be config-driven, rendering a separate verification card per active entry in custom_verifications (supports nominet_contact, nominet_suspended, and in_kyc).
• Add a ContactVerificationNotice component to the domain overview page to alert users when registry verification is required.
• Update the legacy my-sites contact verification card to accept a verificationType prop for per-type copy and document customization.
• Update all test fixtures to use the new property shape.

Why are these changes being made?

The existing domain contact verification system was hardcoded for Nominet (.uk) verification only. To support additional registry-specific verification requirements (e.g., .in domain KYC verification required by NIXI), the frontend needs a generic mechanism. By replacing the two Nominet-specific booleans with a custom_verifications string array, we can support any number of verification types through a single extensible field without future type/schema changes. This is the frontend half of the work; it ships alongside a corresponding backend change that populates the new field.

Testing Instructions

• Verify that .uk domains with active Nominet verification still display the correct verification card with UK-specific copy and accepted documents.
• Verify that .in domains with in_kyc in custom_verifications display the correct verification card with .in-specific copy and accepted documents.
• Verify that domains with no entries in custom_verifications do not show the verification section.
• Verify the domain overview page shows a warning notice when custom_verifications is non-empty.
• Verify file upload and submission works correctly, sending the appropriate verification_type to the API.

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 tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• 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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168661

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168661&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168661&env=a8c-for-agencies

Dashboard live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168661&env=dashboard

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• help-center
• odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/generic-domain-contact-verification on your sandbox.