Improve spaces around MCP Detail spacing

[GenosseOtt]

[andreaskienle]

Fixed the merge conflicts and moved texts to en.json. We can keep the styling like this until we decided on a styling strategy.

[andreaskienle]

@GenosseOtt So, the generic term is Managed Resource, and Providers, ProviderConfigs, and Resources are all (parts of) Managed Resources?

For #2 , I had thought it was the other way around, so I had named the component (and everything related) ManagedResource. In this case, would it make sense to rename it to just Resource?

[enrico-kaack-comp]

I would disagree with the naming. Managed Resources are the resources (K8s resources) that are managed by a crossplane provider (as in that are translated into API requests by the provider and represents a managed service- https://docs.crossplane.io/latest/concepts/managed-resources/).
Providers are a resource defined by crossplane. A specific ProviderConfig is defined by every provider but their meaning is to configure the Provider (like describing with which API the provider should work).

Therefore I suggest the naming:
Crossplane (Top Level)

• Table Providers
• Table Provider Configs
• Table Managed Resources

[GenosseOtt]

Hey, no strong opinion. In the current POC we also called it Crossplane. No complains...

Long term I was hoping to use rather a term reflecting purpose (e.g. Policies) rather than products (e.g. Kyverno).
For Crossplane, given the 3 tables it summarizes, this cannot be fully translated.

No concern with the naming suggested by @enrico-kaack-comp

Therefore I suggest the naming:
Crossplane (Top Level)

Table Providers
Table Provider Configs
Table Managed Resources

[andreaskienle]

@enrico-kaack-comp, @GenosseOtt I changed it to this:

[GenosseOtt]

Thanks. I cannot approve my own request here. But 👍 from my side.