Trident logs are being swallowed

[jldu20]

Describe the bug
Trident logs for errors related to luks volume passphrases are being swallowed.

trident/frontend/csi/node_server.go

Line 1402 in af89a02

return fmt.Errorf("could not set LUKS volume passphrase")

trident/frontend/csi/node_server.go

Line 1867 in af89a02

return fmt.Errorf("could not set LUKS volume passphrase")

Environment
We first noticed this issue in 23.10.0 but we noticed that they still exist.

To Reproduce
Triggering this error. For us, we ran into rate limiting issues which threw this generic error without any other specifics.

Expected behavior
A detailed error telling exactly why this error was being thrown. Our final log should have included client rate limiter Wait returned an error: context canceled

Additional context
Including the error in the returned error should fix this. We just need logs to be more transparent with why something is throwing an issue to help debugging.

[clintonk]

Thanks, @jldu20. No argument on this one, and we should scan/fix all such occurrences.