Compliance report add table

What does this MR do and why?

Update the compliance report to a table to make it easier to read

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Dry run output

gitlab-triage -r ./plugins/all --debug --dry-run -f policies/groups/gitlab-org/compliance-group/compliance-recently-delivered.yml  --source groups --source-id gitlab-org

******************************************************************************************************
Executing policies from policies/groups/gitlab-org/compliance-group/compliance-recently-delivered.yml.
******************************************************************************************************
Performing a dry run.

===============================
Triaging the `gitlab-org` group
===============================

---------------------------------------
Processing summaries & rules for issues
---------------------------------------

----------------------------------------------------------------------
Gathering resources for rule: **Recently delivered compliance issues**
----------------------------------------------------------------------
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/gitlab-org/issues?per_page=100&labels=group%3A%3Acompliance&state=closed&updated_after=2023-03-13
[DEBUG] rate_limit_infos: Rate limit remaining: 1998 (reset at 2023-03-20 17:09:26 +1300)


* Found 44 resources...
* Filtering resources...
* Total after filtering: 20 resources
* Limiting resources...
* Total after limiting: 20 resources

The following issue would be created in project `gitlab-org/govern/compliance/general` for the rule **Recently delivered compliance issues**:

>>>
* Title: 2023-03-20 Recently delivered compliance issues
* Description: Hi @nrosandich

Here is the list of issues delivered the last 7 days in the Compliance group.

Confirm that they have the correct labels ~"workflow::complete"

| Issue | Workflow | Type | Priority |
| --- | --- | --- | --- |
| https://gitlab.com/gitlab-org/govern/compliance/general/-/issues/88+s |  |  |  |
| https://gitlab.com/gitlab-org/govern/compliance/general/-/issues/86+s |  |  |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/395772+s |  | ~"type::maintenance" |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/393625+s |  |  | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/393313+s | ~"workflow::complete" | ~"type::feature" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/392998+s | ~"workflow::complete" | ~"type::maintenance" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/391898+s | ~"workflow::complete" | ~"type::ignore" |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/391259+s | ~"workflow::complete" | ~"type::feature" | ~"priority::3" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/390915+s | ~"workflow::solution validation" | ~"type::feature" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/385694+s | ~"workflow::complete" | ~"type::bug" | ~"priority::1" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/383222+s | ~"workflow::complete" | ~"type::feature" | ~"priority::3" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/373080+s | ~"workflow::blocked" | ~"type::feature" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/373079+s | ~"workflow::ready for development" | ~"type::feature" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/372040+s | ~"workflow::in dev" | ~"type::feature" |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/361435+s | ~"workflow::in review" | ~"type::feature" |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/361424+s | ~"workflow::in review" | ~"type::feature" |  |
| https://gitlab.com/gitlab-org/gitlab/-/issues/354750+s | ~"workflow::scheduling" | ~"type::bug" | ~"priority::4" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/344848+s | ~"workflow::complete" | ~"type::feature" | ~"priority::3" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/331158+s | ~"workflow::planning breakdown" | ~"type::feature" | ~"priority::2" |
| https://gitlab.com/gitlab-org/gitlab/-/issues/327909+s | ~"workflow::complete" | ~"type::bug" | ~"priority::3" |

---

Job URL:

/label

Action items

• If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
• (If applicable) Add documentation to the handbook pages for Triage Operations =>
• (If applicable) Identify the affected groups and how to communicate to them:
  • /cc @person_or_group =>
  • Relevant Slack channels =>
  • Engineering week-in-review