Operator env var changes do not trigger redeployment #304

Problem

When redeploying to a cluster where the operator is already running with the correct image, roxie skips redeployment. This means changes to operator environment variables (e.g., RELATED_IMAGE_* overrides via --operator-env, operandTag, or operandTagOverrides) are silently ignored.

The operator image check (isOperatorImageCorrect) only compares the container image — it does not detect changes in env vars. A user who changes operand tag overrides between deploys will see "Operator already deployed with correct image" and the operator will keep running with the old env vars.

Expected behavior

Changes to the operator's environment configuration should trigger a redeployment (or at least a rolling update of the operator Deployment) so that the new env vars take effect.