Backend configuration example misconfiguration

[gmcbrien]

Describe the bug
NetApp Google Cloud NetApp Volumes backend configuration options and examples refer to the use of storagePools whereas the code example here refers to storagePool.

I assume that this should be an array, which works in my configuration.

I was alerted to this as I could see this field was being ignored in my configuration (which was based on the example provided here).

⚠️ There may be other references that may need adapted. I can only vouch for the GCNV TridentBackendConfig

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

• Trident version: 26.0.
• Trident installation flags used: [e.g. -d -n trident --use-custom-yaml]
• Container runtime: CRIO
• Kubernetes version: v1.31.14
• Kubernetes orchestrator: OpenShift 4.18.18
• Kubernetes enabled feature gates: n/a
• OS: CoreOS
• NetApp backend types: google-cloud-netapp-volumes
• Other:

To Reproduce
Steps to reproduce the behavior:

• Apply sample config, which fails

Expected behavior
A clear and concise description of what you expected to happen.

• Applying the sample config provided should be successful.

Additional context
Add any other context about the problem here.

• It may seem trivial, but this causes effort on the side of the deployer as to why the sample YAML doesn't work as expected.
• ⚠️PR1042 has already been created