Keyword interruptible doesn't affect outdated pipelines triggered by API

Summary

Now it's impossible stop outdated pipelines that were triggered by API using keyword interuptible: true

Steps to reproduce

This job will not stop probably because all its successor have the same checksum

build:
  stage: build
  interruptible: true
  script: do-some-work

Example Project

What is the current bug behavior?

It can be easily reproduced.

What is the expected correct behavior?

Pipelines triggered by trigger API should stop if newer pipeline triggered on the same HEAD

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