Label appears locked before it the MR is merged

Summary

Labels that are locked after they are merged are showing as being locked before they are merged.

Steps to reproduce

1. Create an MR in a project with enforce_locked_labels_on_merge enabled and configured
2. Apply a "type" scoped label
3. Look at the label that will be locked at merge.

Example Project

gitlab.org/gitlab

What is the current bug behavior?

Labels appear to be locked (there's no x to remove it).

What is the expected correct behavior?

Labels should behave normally until the MR is merged.

Relevant logs and/or screenshots

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\\\`)

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