google_netapp_storage_pool does not support specifying a PSA range

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
* Please do not leave _+1_ or _me too_ comments, they generate extra noise for issue followers and do not help prioritize the request.
* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
* If an issue is assigned to a user, that user is claiming responsibility for the issue.
* Customers working with a Google Technical Account Manager or Customer Engineer can ask them to [reach out internally](https://github.com/hashicorp/terraform-provider-google/wiki/Customer-Contact#raising-gcp-internal-issues-with-the-provider-development-team) to expedite investigation and resolution of this issue.

### Description

The google_netapp_storage_pool resource does not support passing the name of of the pre-allocated PSA IP range. This is supported with the API and gcloud.

https://cloud.google.com/netapp/volumes/docs/reference/rest/v1/projects.locations.storagePools#StoragePool

### New or Affected Resource(s)

* google_netapp_storage_pool

### Potential Terraform Configuration

```tf
```

### References

_No response_

b/330932612

Locate the google_netapp_storage_pool resource implementation and its tests; start by tracing how the resource schema maps to the Google NetApp StoragePool API field for the pre-allocated PSA IP range. Done means Terraform can configure that range and the resource tests cover the behavior.

Written by the indexing model from the issue text.