Add support for handling different engines/sources of Policy Reports

[Jonas-Beck]

Currently, the Backstage plugin exposes the EntityKyvernoPolicyReportsContent component that uses the Kyverno source to display Kyverno policies related to the specific Backstage component. We should create additional components for other sources like Trivy and Falco, allowing users to integrate these tools with their Backstage instance if they use them.

This would also make it easier to change the view based on the best way to present policies related to each source.

Additionally, it might make sense to make the component naming more consistent when adding more sources. Suggested naming conventions could be:

• EntityKyvernoPoliciesContent
• EntityTrivyPoliciesContent
• EntityFalcoPoliciesContent

[Jonas-Beck]

Component naming has been updated in #4

[Jonas-Beck]

@Jaxwood Do you think we should create an EntityCustomPoliciesContent component that would allow users to define their own sources and display the policies using a standard view? users could then create an issue if they think that a specific component should be created for their source and what it should look like.

The reason I wanted to create separate components for each source was because I thought it would make sense to display policies for some sources differently and potentially include information related to the source, like links to documentation.

[Jaxwood]

@Jonas-Beck sounds like a good idea 👍