Remove compliance FE/BE specific verification

What does this MR do and why?

With recent changes to compliance verification process (Move compliance verification processor to own f... (!2071 - merged)) we have noticed a that certain individuals (fullstack) are being over weighted verification issues. This MR removes frontend (FE) and backend (BE) and moves all engineers to fullstack (FS). This will hopefully even out the verification process. Also verifications for FE or BE should be able to be verified by the other, good cross over collaboration.

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-policies-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.

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