Update frontend to use new license compliance backend values

What does this MR do and why?

Updates the UI to use allowed and denied instead of approved and blacklisted. Behind a feature flag lc_remove_legacy_approval_status

Screenshots or screen recordings

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

How to set up and validate locally

• In rails console, enable the feature flag Feature.enable(:lc_remove_legacy_approval_status)

• Download and set up imported project. 2022-03-14_18-24-994_fernando_march-security-report_export.tar.gz

• Run a pipeline on Master. Wait until it completes

• From the left Nav go Security & Compliance -> License Compliance

• Verify you can add licenses, remove licenses, add security approvers.

• Create a new branch, and and edit the package.json to add a new dependency.

• Create a new MR.

• Wait for the MR to have it's test pipeline complete

• Verify you can see licenses like in the screenshot

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #335868 (closed)