Add Hull testing to OPA Gatekeeper charts

[MKlimuszka]

No description provided.

[doflamingo721]

The hull testing coverage 100% coverage for the gatekeeper chart is not possible at the moment because of multiple issues in the upstream and rancher's gatekeeper template. Some of the issues are already logged (#41688 and #41689) but similar indentation and tolerations from values.yaml not getting applied to the templates issues still persist in other templates as well. Some fixes are already raised in the upstream chart for this (open-policy-agent/gatekeeper#2817 and open-policy-agent/gatekeeper#2862) but these fixes would be released with the new gatekeeper chart. As of now the chart coverage is at 97 percent.
I'd suggest merging the PR at 97 percent coverage and with coverage disabled so that it won't affect the ci builds.
Edit: The PR cannot be merged since it has a failure which will cause every ci build to fail if we merge this PR as it is.
@eliyamlevy @gunamata What do you think should be the right approach?

[Jono-SUSE-Rancher]

@MKlimuszka - We cant keep this in v2.7.7. If we're blocked by upstream (or blocked by the CI build failures. Can we determine what the course of action here is and remove it from v2.7.7?
cc @doflamingo721

[mitulshah-suse]

@gunamata @diogoasouza Can you please advise about the below. As we had discussed earlier, this cannot be pushed in yet, due to upstream fixes pending and the handover for these have already been given to your team. So i believe your team will need to take this further.
cc: @Jono-SUSE-Rancher

[gunamata]

@mitulshah-suse , the indentation issue (#41689) has been resolved but we did not yet get a chance to work on #41688 . We will add this to our list of Q1 items. Removing the milestone 2.7.7 and put it under 2024-v2.8x-Backlog

[mitulshah-suse]

@gunamata Ok, we are unassigning ourselves from this issue as well, since your team will be working on it once upstream issues are fixed.

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.