Updates to migration content

[jennifer-shehane]

1. At the beginning, it's stated that there are 5 steps for migrating. Then there are many many more sections within and after outlining these 5 steps that make the process of migration confusing.

The steps outlined were:

1. Update your configuration file, cypress.json by default, to remove experimentalComponentTesting
2. Install updated dependencies
3. Update the plugins file
4. Use CLI commands to launch
5. Update the support file (optionally)

But then there are more sections for Expanded stylesheet support (within the steps), Desktop GUI no longer displays component tests, Executing all or some component tests, Coverage, etc etc etc.

We need to be very clear about the steps required to take for migration. People do not want to spend their time reading about implementation details or niceties of the new component testing. They need migration to be clear and as quick as possible so things won't break.

This is extra important considering all of the other breaking changes along with it. I would recommend

• Cut down the content to the bare necessary and when possible refer to the component testing docs for extra detail (like the cypress.json overrides and testingType - this is already documented elsewhere and is not a breaking change needed for migration).
• Do not explain implementation details on 'why' a change was made. Simply state the action they need to take to get their code working.

---

2. The Component Testing needs to be a single section within the 7.0 Migration - there are several sections within 7.0 that people need to be aware of altogether.

New hierarchy