Update wording of 'rename specs' area when the specs are not actually being renamed

[sync-by-unito]

Summary

I know this step is for renaming and moving but it feels odd to have everything say ‘rename’ when in this case there isn’t a rename and just a move:

https://cypressio.slack.com/archives/C02MYBT9Y5S/p1652990922196199

Acceptance Criteria

If we are not renaming the spec extension (like for an existing Dashboard project)

1. Have heading say ‘Move existing specs’
2. Have sub description say ‘In this step, we’ll automatically move your existing spec files.
3. Remove the sub-heading in the content that says ‘We recommend automatically…..etc'

┆Issue is synchronized with this Jira Task by Unito
┆Attachments: Screen Shot 2022-05-19 at 2.07.18 PM.png
┆author: Matthew Schile
┆epic: UI/UX Improvements
┆friendlyId: UNIFY-1801
┆priority: Medium
┆sprint: Fast Follows 1
┆taskType: Task

[lmiller1990]

I thought this was a quick win but it's actually quite involved - we need a lot of conditionals, and there's not an easy way to know if we are doing a rename or a move (or both) - eg, there's no "is renaming" or "is moving" flag. I think the value of the recommended change in the acceptance criteria relative to the actual work involved and the impact is not worth it.

Instead, I changed it to be generic phrase that works for both rename and/or move. I think this is good enough to make the actual intent clear (we are changing to specs to match our convention) without been confusing.

[cypress-bot]

The code for this is done in cypress-io/cypress#22325, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[emilyrohrbough]

This was released in 10.2.0.