Upgrading helm chart from 100.2402.0 to 100.2406.1: new flag configurator-reconcile-interval breaks pod startup

[drew0ps]

Describe the bug After upgrading the helm chart to the version 100.2406.1 from 100.2402.0 the pod startup of trident-operator is failing. Error message:

 k logs trident-operator-7765b66cfd-nkrlm -n k8s-trident 
flag provided but not defined: -configurator-reconcile-interval
Usage of /trident-operator:
  -debug
        Set log level to debug, takes precedence over log-level
  -k8s-api-server string
        Kubernetes API server address
  -k8s-config-path string
        Path to KubeConfig file
  -log-format string
        Logging format (text, json) (default "text")
  -log-level string
        Logging level (trace, debug, info, warn, error, fatal) (default "info")
  -skip-k8s-version-check
        (Deprecated) Skip Kubernetes version check for Trident compatibility

I have noticed that this is a newly added flag: https://artifacthub.io/packages/helm/netapp-trident/trident-operator?modal=template&template=deployment.yaml&compare-to=100.2402.0 and it has a default value: https://artifacthub.io/packages/helm/netapp-trident/trident-operator?modal=values&compare-to=100.2402.0

Environment Provide accurate information about the environment to help us reproduce the issue.

• Trident version: default values
• Trident installation flags used: default values
• Kubernetes version: 1.29.6
• Kubernetes orchestrator: PKS

To Reproduce

1. Install helm chart 100.2402.0
2. Upgrade to 100.2406.1
3. Inspect the pods and the logs

Expected behavior The operator pod is running

Additional context Add any other context about the problem here.