feat: Introduce LiqoInfo CRD for cross-cluster version reporting

[thisiskazem]

Describe the problem you are having (if any)

Currently, there is no automated mechanism to programmatically verify the Liqo version of a remote cluster from the local control plane.
This makes it difficult to ensure version compatibility before performing a local cluster upgrade, potentially leading to breaking peerings if versions are incompatible.

Describe the solution you would like

Introduce a new replicated CRD named LiqoInfo that stores the cluster's Liqo version and other relevant metadata.
This resource should be automatically created upon peering and replicated to the remote cluster via the CRD-Replicator.

Describe the user value of this feature

Operators can programmatically check the compatibility of all peered remote clusters before upgrading a local Liqo instance.
This reduces the risk of downtime or broken multi-cluster connectivity caused by version mismatches.

Describe your proposed solution

• New CRD: Define LiqoInfo (namespaced) to hold cluster metadata (e.g., version, clusterID).

• Operator Logic: Add a controller that triggers when an Identity Secret is created, generating a LiqoInfo resource in the corresponding tenant namespace.

• Replication: Grant the crd-replicator permissions to watch and replicate LiqoInfo resources across clusters.

• ForeignCluster Integration: Update the ForeignCluster controller to read the replicated LiqoInfo from the remote cluster and populate the ForeignCluster.Status with the remote version.

Do you volunteer to implement this feature?

• I want to implement this feature

Code of Conduct

• I agree to follow this project's Code of Conduct