Feat: Data structure of Repository is changed in backend, UI needs to make compatibility change

[xingzhang-suse]

The registries CRD is changed by backend

repositories: String[];

to

repositories : [{
  name: String,
  matchConditions: [{
    name: String,
    expression: String
  }]
}]

The datasource definition of registry list table needs to be changed for repositories column.

The matchCondition does not need to be implemented in UI in the registry edit page, but it needs to be confirmed the field can be configured in edit yaml page. (Ref: Slack record)

[williamshen9999]

with 0.5.0-rc2, the repositories structure is correctly changed by UI.

root@sbom-rke2-213-0121:~# k get registry test-cabundle -o yaml
apiVersion: sbomscanner.kubewarden.io/v1alpha1
kind: Registry
metadata:
  creationTimestamp: "2026-01-22T08:47:22Z"
  generation: 5
  name: test-cabundle
  namespace: default
  resourceVersion: "555399"
  uid: 141a48b3-e4a1-4db5-90c5-e6a5dc3ad4b8
spec:
  authSecret: ""
  caBundle: ""
  catalogType: OCIDistribution
  insecure: true
  platforms: []
  repositories:
  - name: nvlab/ubuntu
  uri: 10.115.54.173:5000