Coverage-check approval rule can not be accessed in EE Premium

Summary

According to the doc and release note, the coverage check approval rule is a feature in EE Premium, however this feature can only be accessed in EE Ultimate.

See code: https://gitlab.com/gitlab-org/gitlab/-/blob/6184e4018e2000e1ecb8a49a797d3e437cdd7a61/ee/app/models/license.rb#L189

Steps to reproduce

• Config Coverage-Check approval rules in a premium plan's project general setting.

• Create a merge request and expand the View eligible approvers

Example Project

https://jihulab.com/xg-premium-test/coverage-test/-/merge_requests/2

What is the current bug behavior?

The Coverage-Check approval rules is not displayed

What is the expected correct behavior?

The Coverage-Check approval rules should work and be displayed

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

Version:        14.8.0-pre
Revision:       84105b97854
Directory:      /Users/qiankun/IdeaProjects/gitlab-development-kit/gitlab
DB Adapter:     PostgreSQL
DB Version:     12.6
URL:            http://127.0.0.1:3000
HTTP Clone URL: http://127.0.0.1:3000/some-group/some-project.git
SSH Clone URL:  ssh://git@127.0.0.1:2222/some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2

(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

Possible fixes

The approval rules is currently generated under GitLab Ultimate. To "downgrade" this feature, we will need to:

1. Create a new feature keyword (report_approval_coverage) in our EEP License
2. Generate an approval rule if our new feature report_approval_coverage license is supported.