NACK Stream resource spec updated with empy values

[kejne]

What version were you using?

0.18.2

What environment was the server running in?

Kubernetes 1.33 & equivalent kind cluster

Is this defect reproducible?

• Create a stream with only required fields set
• Let NACK reconcile the stream
• Observe the stream

Given the capability you are leveraging, describe your expectation?

The reconciliation should not alter the spec, but rather only the status of the CR since it would otherwise drift when using GitOps tools such as ArgoCD.
The stream object should be identified as "in sync" after a reconciliation.

Given the expectation, what is the defect you are observing?

When creating a stream with default configuration, the operator will after reconciliation have set all the fields to their nil or empty value and populate it back to the CR.
This always happens.