[EPIC] Add Visual Ressource Graph back to the MCP Detail screen

[GenosseOtt]

Description
An often requested feature is the resource graph that we had as a POC in earlier versions.

It shows the dependencies between different resources., helping human end users to visually understand what is being orchestrated by their instance of ManagedContorlPlane

Technical Tasks, Steps

• parse the dependencies between resources, how generic we could write it or if we need provider specific logic in it.
  A generic approach might be e.g. the metadata.ownerReferences or a field ...Ref: with a name, namespace key.

• rework the graph view. Check the library for license and quality, rework the code and bring it from poc state into stable state.

Technical Notes

• We are using Lib: https://reactflow.dev/

Order Options:

Generic

• All managed resources shown, items in Graph are outlined according to the Crossplane Provider used.
• Give Proider a color bar based on its provider

ProviderConfig

• Show all managed ressources, Create one Graph Tree per ProviderConfig (Hint: no ProviderConfigref means default)

Helm charts used

• Show all managed ressources, Create one Graph Tree per HelmChart (Hint: see metadata.labels)

GitOps, Flux Integrations

• Show all managed ressources, Create one Graph Tree per Flux (Hint: see metadata.labels)

Out of scope

• OCM Package View
• Landscaper View
• Kyverno View

Done Criteria

• Graph View is back on top of MCP Detail view
• On click on item, show the YAML detail modal
• On Item, show item health (lets pull in UI for Item box)
• Graph can be shown horizontally or vertically
• Graph component is maintainable, tested, clean
• Order Options are available [Work in seperate items, releasable as soon as Generic order is available, rest over following updates]

[In-Ko]

Since this is an Epic, I suggest we try to break it down a bit ? Maybe after a first evaluation of the existing code ? At least I have the feeling that the whole Epic is to big to be "sprintable", or ?

[andreaskienle]

I just moved this back to Active Epics because we have some sub-issues