Error when trying to add new Compliance Framework to top level namespace with premium subscription

Summary

When trying to create a new Compliance Framework on the top level namespace with a premium subscription the error Pipeline configuration full path feature is not available is returned.

Steps to reproduce

1. on a top level namespace with a GitLab Premium subscription follow the steps in Compliance frameworks
2. populate the fields Name and Description but leave Compliance pipeline configuration (optional) blank (as this is a GitLab Ultimate feature)
3. click Add Framework

A banner is displayed with the error Pipeline configuration full path feature is not available

Example Project

This can be reproduced on any top level namespace which has a GitLab Premium subscription. For example on Gitlab Silver (internal)

What is the current bug behavior?

It is not possible to add new Compliance Frameworks when on a premium subscription.

What is the expected correct behavior?

This should be successful as it is a premium feature.

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