Integration status breaking change since Camel-K client v2.5.0

I'm testing out YAKS on my k8s platform with Camel-K client v2.5.0, Camel-K runtime version v3.15.0 and Camel v.4.8.0. The same test which passes on Camel-K client v2.4.0, results in the following error when verifying an integration is running:


This happens for any tests which attempts to check the status of an integration, my failing step specifically is _**Then** Camel K integration xkcd-source-log-sink should be running._

YAKS is not expecting this new field 'catalog' which is present from this version onwards when checking an integration's status:
https://github.com/apache/camel-k/blob/v2.5.0/pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml#L56

Could we perhaps fix this by marking unknown fields as ignorable? Otherwise, when do you reckon a new release of YAKS which bumps to latest Camel and Camel-K versions will be released? Just looking for rough timelines in order plan our own upgrades.

Thanks in advance.

Start at the Camel K integration-status verification used by the step “Then Camel K integration xkcd-source-log-sink should be running,” and compare its handling with the Camel-K v2.5.0 CRD at pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml#L56. Done means status checks tolerate the added catalog field and regression coverage confirms integrations are still recognized as running.

Written by the indexing model from the issue text.