Make a plan to begin designing the switching experience for DNS hosting

[h-m-f-t]

Issue description

The first section of the DNS hosting 2.0 summary paper outlines the requirements for a switching experience (including "switching away"). Let's re-review the paper and begin planning to break down our approach to designing the UI/UX.

Initially, this should focus on the "Choose to use" step, followed by "DNS record preparation > Manual addition", and then "NS record switch".

Acceptance criteria

• A written plan, FigJam board, or GitHub issues exist to begin the design work
  • This can be as simple as a few issues, some sketches or wireframes in FigJam, or a plan to make those things
  • Consult with Engineering as needed
• Confirm the approach with Product, who will help prioritize next steps.

Additional context

At this stage, let's assume that users are already in the enterprise mode experience (something that is a work in progress; see #5329). We can consider still within the legacy experience, but Product anticipates very little UI changes there to signal DNS hosting availability (e.g., maybe an info banner to spur them contacting us so we can consider making a portfolio).

Links to other issues

No response