Re-evaluate environment Rollback behavior

Problem Statement

The current behavior of environment rollback is unclear.

Coming from #31649 (comment 222134259)

The current behavior is that it basically retries the pipeline job i.e. triggers a new deployment with an old code (SHA). This essentially is correct in terms of rollback mechanism and the UI reflects the states, however, it might be confusing as it states in the issue description.

Expected:

Reach

CI users wishing to perform rollback 3.0 = Significant reach (~25% to ~50%).

Impact

0.5 = Low impact as the user can perform this action today but it is confusing

Confidence

80% = Medium confidence

Effort