Fix Node Driver Crash Caused by Auto-Select Protocol

[sakshi-garg1]

Description

This PR addresses the issue of the node pod crashing when the X_CSI_TRANSPORT_PROTOCOL is empty in the powermax-array-config. The fix ensures that when the protocol is unspecified, the driver will prioritize available protocols in the following order:

• NVMe/TCP
• FC
• iSCSI

The driver will automatically select the first available and working protocol from this list, establishing a connection based on these preferences.

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1689
dell/csm#1725

Checklist:

• Have you run format,vet & lint checks against your submission?
• Have you made sure that the code compiles?
• Did you run the unit & integration tests successfully?
• Have you maintained at least 90% code coverage?
• Have you commented your code, particularly in hard-to-understand areas
• Have you done corresponding changes to the documentation
• Did you run tests in a real Kubernetes cluster?
• Backward compatibility is not broken

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• X_CSI_TRANSPORT_PROTOCOL empty with NVMe/TCP configured/ driver installed and running successfully + cert-csi
• X_CSI_TRANSPORT_PROTOCOL empty with FC configured/ driver installed and running successfully + cert-csi
• X_CSI_TRANSPORT_PROTOCOL empty with iSCSI configured/ driver installed and running successfully + cert-csi