Adherence report v2

The new adherence report will be based on Requirements statuses See the table in the design section Most likely we will use REST api for this table for better performance the response will look like:

[
   {
      "name":"projectA",
      "frameworks":[
         {
            "Name":"FrameworkA",
            "Description":"Description of Framework A",
            "Requirements":[
               {
                  "Name":"Req A",
                  "Description":"Description of requirement A",
                  "Status":"2/2",
                  "checks":[
                     {
                        "enum":"at_least_two_approvals",
                        "name":"At least two approvals on MRs",
                        "status":"SUCCESS",
                        "date":"2024-10-19"
                     },
                     {
                        "enum":"prevent_approval_by_merge_request_author",
                        "name":"Prevent authors to approve",
                        "status":"SUCCESS",
                        "date":"2024-10-19"
                     }
                  ],
                  policies_ids: [1,2,3]
               }
            ]
         },
         {
            "Name":"FrameworkB",
            "Description":"Description of Framework B",
            "requirements":[
               {
                  "Name":"Req B",
                  "Status":"0/1",
                  "Checks":[
                     {
                        "enum":"at_least_two_approvals",
                        "name":"At least two approvals on MRs",
                        "result":"FAIL",
                        "date":"2024-10-19"
                     }
                  ],
                  policies_ids: [4]
               }
            ]
         }
      ]
   }
]

Group > Subgroup > Project centres should show only corresponding requirements Grouping, filtering and pagination are not part of this issue

Details in the designs #452306 (designs)