Unable to delete "Severity" criteria from Security Policy rule using delete icon

Summary

When creating a security policy and choosing the criteria for Severity, you can Clear all to remove all status options and the yaml updates in realtime.

However, we present the user with a trashcan icon. Once Severity is selected you can no longer delete it with the trashcan icon.

Steps to reproduce

Create a scan result policy, add the Severity criteria, attempt to delete it.

Example Project

What is the current bug behavior?

See a walkthrough in Loom

Walkthrough 2

What is the expected correct behavior?

Clicking the trashcan icon should result in deleting the rule and update the yaml.

Relevant logs and/or screenshots

Loom shared above.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Experienced this in GitLab.com.

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes