Clean up License Compliance widget dependency list

What does this MR do and why?

• Removes the clutter of having full dependency lists for each category of license detected. We only show the full list of dependencies for denied licenses.

• For Uncategorized or Allowed licenses we provide a count of dependencies and a link to the full report.

• Removes legacy blacklisted and approved references that were removed a few milestones ago.

Describe in detail what your merge request does and why.

Screenshots or screen recordings

header	After
- (Page is existing, same link as Full Report)

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

How to set up and validate locally

• Reach out to me for a demo, or attempt steps below
• In a rails console enable flag Feature.enable(:refactor_license_compliance_extension)
• Clone the https://gitlab.com/gitlab-examples/security/security-reports project locally
• Manually trigger the pipeline to run for Master. This can be done by going to the CI/CD -> Pipelines tab on the left nav and then clicking the Run Pipeline button.
• Set up Allowed/Denied licenses in https://<localhost>/<group>/<project>/-/licenses#policies
• Create a new MR. I suggest changing something simple like a letter or two in the README.md file. We just need a pipeline to complete and run. The sample project uses test reports to generate the data so doesn't matter what you change just need a MR.
• Go to the MR and look for the license compliance widget.

Numbered steps to set up and validate the change are strongly suggested.

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 #356334 (closed)