Issue Summary

With new ITSM feature on JSD, additional field - "deployment_gate_enabled" is added to Pipelines' deployment environment.

However, this field can be updated through API (/2.0/repositories/<workspace>/<repo_slug>/environments/ ) even thou the repository is not linked to Jira's ITSM project.
This will block Pipelines build from deploying to the environment with the "Change request pending" prompt.

In addition to it, it's not possible for users to check or toggle the deployment gating flag on Deployment Settings to continue with the build

Steps to Reproduce

1. Run the API /2.0/repositories/<workspace>/<repo_slug>/environments/ with the following payload

   {
         "deployment_gate_enabled": true,
         "environment_type": {
           "type": "deployment_environment_type",
           "name": "Test",
           "rank": 0
         },
         "name": "Test"
       }
   

   Repo shouldn't connect to any Jira ITSM project while reproducing the issue

2. Navigate to "Repository Settings>Deployment" and there's no option for users to toggle off the deployment gating flag
   

Expected Results

"deployment_gating" flag auto-set as "false" if the repo is not linked to Jira ITSM project or Jira criteria are not met.

Actual Results

The API request able to parse "deployment_gate_enabled" as true, which will block Pipelines build to deploy to the specific deployment environment.
And there's no option on UI for users to turn off the feature for the deployment environment.

Workaround

• UI: Re-add the deployment environment through UI
• API: Run API to delete the deployment environment, then run POST request the add new deployment environment with the "deployment_gate_enabled" field as "false"