CRD in Operator 0.25.5 have invalid value for watched namespaces

After upgrading from ClickHouse Operator 0.25.3 to 0.25.5, our previous ClickHouseOperatorConfiguration manifests—valid and working on 0.25.3—are now rejected due to a breaking change in the CRD schema for the watch.namespaces field.

This is a YAML snippet of the relevant configuration (which worked in v0.25.3):

apiVersion: clickhouse.altinity.com/v1
kind: ClickHouseOperatorConfiguration
# ...
spec:
  # ...
  watch:
    namespaces:
      - clickhouse

• In 0.25.3, the CRD defines spec.watch.namespaces as an array of strings.
• In 0.25.5, this changed to an object (type: object), breaking compatibility with configurations that previously used the old array format or documentation that expected one behavior.

CRD change that caused breakage:

• 0.25.3 CRD lines:

namespaces:
  type: array
  description: "List of namespaces where clickhouse-operator watches for events."
  items:
    type: string

• 0.25.5 CRD lines:

namespaces:
  type: object
  description: "List of namespaces where clickhouse-operator watches for events."
  x-kubernetes-preserve-unknown-fields: true

Compare deploy/operatorhub/0.25.3/clickhouseoperatorconfigurations.clickhouse.altinity.com.crd.yaml with the 0.25.5 CRD sections linked in the issue, then inspect the surrounding CRD generation or operator configuration code. Verify that the intended schema accepts the previously valid watch.namespaces manifest and that the resulting CRD and documentation agree.