Docs - product feedback: Environment scope filter does not work on Group scope variables

Summary

Group level CI/CD variables accept the environment scope parameter. You can successfully POST a variable but when you try to update it with a PUT request the environment_scope filter does not work.

Steps to reproduce

1. Create two Group level CI/CD variables with the same name and different scopes.
2. Try to a update them with PUT request while applying the environment_scope filter https://gitlab.com/api/v4/groups/Infra/variables/AWS_SECRET_ACCESS_KEY?filter[environment_scope]=test

Example Project

What is the current bug behavior?

The environment_scope filter is ignored.

What is the expected correct behavior?

Apply the environment_scope filter and update the correct variable

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

GitLab Enterprise Edition 14.6.3-ee

(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