[CRD-v1] Try to enforce the Connect topic names or make better defaults

[scholzj]

When running multiple Connect or MM2 clusters, the common issue is that the users have misconfigured the names of the topics used by the Connect cluster, because the defaults have a static value independent on the namespace / cluster name.

We should consider if we can improve this as part of the migration to v1 CRDs. The CRD migration might give us an opportunity to get all users to configure the topics in .spec.config and make the config required? Another option might be to have a better default names for the topics, but that would likely need to include namespace, deployment type (MM2/Connect) and cluster name.Anr even that might not work well across Kube clusters

[scholzj]

Discussed on the community call on 16.5.2024: This would be useful to have. But we should have a proposal to clarify how will we actually address this.

[maakuth]

Here's a good reference for all the internal topics that MM2 uses: https://developers.redhat.com/articles/2023/11/13/demystifying-kafka-mirrormaker-2-use-cases-and-architecture#mirrormaker_2_internal_topics

I think each of them should be in strimzi's tighter leash.