Describe the bug
In the new version of Trident (25.02.0), the trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource. When an imageRegistry is specified, all CSI-sidecar containers in the Kubernetes manifest are set to use the image from the imageRegistry. However, the image names and tags are not correctly populated, leading to incorrect image references.

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

• Trident version: 25.02.0
• Kubernetes version: 1.30.4

To Reproduce

1. Deploy Trident 25.02.0 with trident-operator.
2. Create a TridentOrchestrator resource with a specified imageRegistry.
3. Observe the generated Kubernetes manifest for CSI-sidecar containers.

Expected behavior
The CSI-sidecar containers should use the specified imageRegistry along with the correct image names and tags.

Actual Behavior
The CSI-sidecar containers are set to use the imageRegistry but lack the correct image names and tags, resulting in invalid image references.