[CI] Trident-node-linux pods are in crashloopbackoff

Trident-node-linux pods are in crashloopbackoff in our CI

trident                             trident-node-linux-2lmw6                                                     0/2     CrashLoopBackOff   7 (118s ago)    17m     192.168.100.23   mgmt-2246749023-kubeadm-capm3-virt-management-cp-0   <none>           <none>
trident                             trident-node-linux-8vc6s                                                     0/2     CrashLoopBackOff   7 (2m18s ago)   17m     192.168.100.20   mgmt-2246749023-kubeadm-capm3-virt-management-cp-1   <none>           <none>
trident                             trident-node-linux-dkghd                                                     0/2     CrashLoopBackOff   7 (2m13s ago)   17m     192.168.100.22   mgmt-2246749023-kubeadm-capm3-virt-management-cp-2   <none>           <none>
trident                             trident-node-linux-xxlw7                                                     0/2     CrashLoopBackOff   7 (2m9s ago)    17m     192.168.100.21   mgmt-2246749023-kubeadm-capm3-virt-management-md-0   <none>           <none>

Although this does not block deployment, it is not very elegant.

  Warning  Failed             28h                  trident-crd-controller  Failed to create backend: problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver; could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post "https://192.168.70.7/servlets/netapp.servlets.admin.XMLrequest_filer": context deadline exceeded

time="2026-01-06T09:57:35Z" level=warning msg="Could not update Trident controller with node registration, will retry." error="failed during retry for CreateNode: could not log into the Trident CSI Controller: error communicating with Trident CSI Controller; Put \"https://100.73.233.249:34571/trident/v1/node/mgmt-2246749023-kubeadm-capm3-virt-management-cp-0\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" increment=2m3.13920697s logLayer=csi_frontend requestID=4ff61fbd-212f-427a-b81f-bf734b92ec96 requestSource=Internal workflow="plugin=activate"
==== END logs for container trident-main of pod trident/trident-node-linux-2lmw6 ====
==== START logs for container node-driver-registrar of pod trident/trident-node-linux-2lmw6 ====
I0106 09:55:42.894828   37885 main.go:154] "Version" version="v2.15.0"
I0106 09:55:42.894896   37885 main.go:155] "Running node-driver-registrar" mode=""
I0106 09:55:42.894901   37885 main.go:176] "Attempting to open a gRPC connection" csiAddress="/plugin/csi.sock"
I0106 09:55:52.896005   37885 connection.go:253] "Still connecting" address="unix:///plugin/csi.sock"
I0106 09:56:02.895052   37885 connection.go:253] "Still connecting" address="unix:///plugin/csi.sock"
I0106 09:56:12.896160   37885 connection.go:253] "Still connecting" address="unix:///plugin/csi.sock"
E0106 09:56:12.896185   37885 main.go:180] "Error connecting to CSI driver" err="context deadline exceeded"

cc @sakuchoudhary98 @ravin57