DCOS-57015: Jobs - Enable/Disable Schedule sets concurrencyPolicy to ALLOW

[GeorgiSTodorov]

Persist concurency policy when enabling and
disabling schedule using the dropdown.

Closes https://jira.mesosphere.com/browse/DCOS-57015

Testing

0. Go to Jobs tab.
1. Create a job with a schedule (doesn't matter if it is enabled or not). It just has to have "Concurrency Policy" set to false.
   Example JSON:

{
  "id": "new-job-1",
  "run": {
    "cpus": 1,
    "mem": 128,
    "disk": 0,
    "gpus": 0,
    "cmd": "sleep 1000",
    "artifacts": [],
    "maxLaunchDelay": 3600,
    "restart": {
      "policy": "NEVER"
    },
    "ucr": {
      "image": {
        "id": "nginx",
        "kind": "docker",
        "forcePull": false
      },
      "privileged": false
    }
  },
  "schedules": [
    {
      "id": "123",
      "cron": "1 2 3 4 5",
      "timezone": "UTC",
      "startingDeadlineSeconds": 900,
      "concurrencyPolicy": "FORBID",
      "enabled": false,
      "nextRunAt": "2020-04-03T02:01:00.000+0000"
    }
  ]
}

2. Go to that job's detail screen.
3. Use the actions dropdown on the top right to enable or disable the schedule.
4. Open the job and verify that Concurrency Policy did not change to true.

Trade-offs

None.

Dependencies

None.

Screenshots

Before

After

[mperrotti]

These changes work as expected and code looks good to me. Tagging @natmegs for review because she's spent a lot of time with the Jobs form

[natmegs]

Let's remove this or make the placeholder "ALLOW", as that is what the metronome API defaults to

[GeorgiSTodorov]

Okay, I made it "forbid" since the checkbox is unchecked by default.

Outdated.

[mesosphere-ci]

🎉 This PR is included in version 2.142.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀