Unknown status fields during reconciliation

I am a small operator using this however I am running into the following:

2025-08-19T17:30:57Z    INFO    unknown field "status.conditions"       {"controller": "metricsserver-controller", "object": {"name":"metrics-server","namespace":"kube-system"}, "namespace": "kube-system", "name": "metrics-server", "reconcileID": "37acbbde-7341-41f8-b892-53addd3eba98"}
2025-08-19T17:30:57Z    INFO    unknown field "status.deployedRelease"  {"controller": "metricsserver-controller", "object": {"name":"metrics-server","namespace":"kube-system"}, "namespace": "kube-system", "name": "metrics-server", "reconcileID": "37acbbde-7341-41f8-b892-53addd3eba98"}

It seems that obviously these are missing fields and they come from here:

https://github.com/operator-framework/operator-sdk/blob/v1.41.1/internal/helm/internal/types/types.go#L77-L80

I think it would make sense to extract these fields out into here potentially, or what do we think would be the best approach to take here? I am happy to take on the PR to take care of this.

Start by reading internal/helm/internal/types/types.go at lines 77-80 in operator-sdk v1.41.1 and trace how the helm operator reconciler handles status fields. Reproduce the metrics-server case from the reported log and determine where status.conditions and status.deployedRelease are defined or filtered. Done means reconciliation no longer reports these fields as unknown, with relevant tests updated or added if the repository identifies them.