Expose policy_scope in security policy graphql API

What does this MR do and why?

This MR reinstates the revert MR !146386 (merged) due to gitlab-com/gl-infra/production#17690 (closed)

As a part of Support existing policies as we introduce polic... (#432513 - closed), we want to expose the policy_scope in the graphql query with the compliance frameworks and the projects.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

How to set up and validate locally

1. Create a root level group and create a compliance framework
2. Create Approval policy with policy scope:

type: approval_policy
name: SRP
description: ''
enabled: true
rules:
  - type: scan_finding
    scanners: []
    vulnerabilities_allowed: 0
    severity_levels: []
    vulnerability_states: []
    branch_type: protected
actions:
  - type: require_approval
    approvals_required: 1
    group_approvers_ids:
      - <ID>
policy_scope:
  compliance_frameworks:
    - id: <ID>

3. Enable security_policies_policy_scope feature flag: Feature.enable(:security_policies_policy_scope, group) and enable the Security policy scope experimental feature by going to Settings -> General -> Permissions & Group features -> Select Security Policy Scopes checkbox
4. Go to graphql-explorer and query for approvalPolicies

query{
  group(fullPath:"compliance-policies") {
    approvalPolicies {
      nodes {
        policyScope {
          complianceFrameworks {
            nodes {
              id
              name
            }
          }
          includingProjects {
            nodes {
              id
            }
          }
          excludingProjects {
            nodes {
              id
            }
          }
        }
      }
    }    
  }
}

Addresses #432513 (closed)

changed milestone to %16.10

added Category:Security Policy Management Deliverable Technical Writing UI text automation:ux-missing-labels backend devopsgovern docs-channel frontend groupsecurity policies sectionsec typefeature workflowin dev + 1 deleted label

assigned to @sashi_kumar

removed frontend label

removed UI text label

removed Technical Writing label

removed 1 deleted label

removed automation:ux-missing-labels label

removed docs-channel label

@mc_rocha Since you already have context on this, would you mind taking an initial look?

requested review from @mc_rocha

added documentation label

	1 Message
📖	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/graphql/reference/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@joseph (UTC+0, same timezone as author)	@hraghuvanshi (UTC+5.5, 5.5 hours ahead of author)

Please check reviewer's status!

• Reviewer is available!
• Reviewer is unavailable!

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger

mentioned in issue #444227 (closed)

added 1 commit

• 87f5ce3b - Refactor spec and update doc

Compare with previous version

changed the description

approved this merge request

added pipeline:mr-approved label

👋 @mc_rocha, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, a new pipeline will be started shortly.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

requested review from @Andyschoenen and removed review request for @mc_rocha

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: ✅ test report for 87f5ce3b

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Govern      | 66     | 0      | 0       | 0     | 66    | ✅     |
| Create      | 8      | 0      | 3       | 0     | 11    | ✅     |
| Package     | 0      | 0      | 1       | 0     | 1     | ➖     |
| Plan        | 4      | 0      | 0       | 0     | 4     | ✅     |
| Monitor     | 4      | 0      | 0       | 0     | 4     | ✅     |
| Data Stores | 2      | 0      | 0       | 0     | 2     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 84     | 0      | 4       | 0     | 88    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: ✅ test report for 87f5ce3b

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Govern      | 272    | 0      | 19      | 0     | 291   | ✅     |
| Create      | 153    | 0      | 20      | 0     | 173   | ✅     |
| Package     | 0      | 0      | 2       | 0     | 2     | ➖     |
| Plan        | 8      | 0      | 0       | 0     | 8     | ✅     |
| Monitor     | 8      | 0      | 0       | 0     | 8     | ✅     |
| Data Stores | 4      | 0      | 0       | 0     | 4     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 445    | 0      | 41      | 0     | 486   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

approved this merge request

resolved all threads

enabled an automatic merge when the pipeline for 745122ff succeeds

merged

mentioned in commit ac499bf2

added workflowcanary label and removed workflowin dev label

added workflowproduction label and removed workflowcanary label

mentioned in merge request !146721 (merged)

mentioned in merge request !145182 (closed)

mentioned in merge request kubitus-project/kubitus-installer!2869 (merged)

added releasedpublished label

added pipelinetier-3 label