Resolve "AutoDevOps stop action for staging and production environments"

What does this MR do?

Add stages for stop the production and staging deployments, currently there aren’t stop actions for those environments.

Screenshots or Screencasts (strongly suggested)

1. Deploy the application using the AutoDevOps template.

2. Go to the Environment Panel and check the deployed application

3. Stop the environment by click on the red square stop button ⏹ and you get the alert

4. Proceed anyway and there is any available environment anymore

5. Go to the Stopped environment and you see the production that has been stopped.

6. Click on the arrow button to go and check the environment, is there still alive, even though is listed as stopeed

How to setup and validate locally (strongly suggested)

1. Create a project where we can deploy an application with AutoDevOps
2. Deploy an application with the following deployment strategies,

• Continuous deployment to production
• Automatic deployment to staging and manual deployment to production

3. Stop the production and staging deployment with the stop_action buttons this MR adds.
4. Confirm that the deployments have been stopped properly.

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #339365 (closed)