Improve wording in modal when redeploying environments

Release notes

We've improved the copy in the Re-deploy and Rollback Environment modals to deliver a more consistent experience so that users can better understand what actions to take when fixing a problem with a deployment.

Problem to solve

Clarify the wording to make users understand that redeploying an environment is different from rolling it back.

Details

On the Environments page, the copy reads:

Re-deploy environment production?

This action will relaunch the job for commit 21d15a1e, putting the environment in a previous version. Are you sure you want to continue?

The use of "previous version" is confusing. The user may need to redeploy the most recent commit in a pipeline and the language makes it sound like it will be rolled back instead.

Screencast_2022-03-22_10_06_43

Proposal

In the environments page, and detail page, when rollback and re-deploy options are available, the modal copy should be updated to reflect the following:

Re-deploy modal

Modal title: Re-deploy environment <environment_name>?
Modal message: This action will retry the latest deployment with the commit <commit_ID> for this environment. Are you sure you want to continue?
Actions:
- Cancel
- Re-deploy environment

Rollback modal

Modal title: Rollback environment <environment_name>?
Modal message: This action will roll back this environment next to a previously successful deployment for commit <commit_ID>. Are you sure you want to continue?
Actions:
- Cancel
- Rollback environment

Include link to the documentation: https://docs.gitlab.com/ee/ci/environments/#retry-or-roll-back-a-deployment