@google-maps/addressvalidation sporadic RST_STREAM for `validateAddress` call.

Thanks for stopping by to let us know something could be better!

Maybe similar to https://github.com/googleapis/google-cloud-node/issues/4679 but different package.

```
Error: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)
at callErrorFromStatus (/opt/app/node_modules/@grpc/grpc-js/src/call.ts:81:17)
at Object.onReceiveStatus (/opt/app/node_modules/@grpc/grpc-js/src/client.ts:356:55)
at Object.onReceiveStatus (/opt/app/node_modules/@grpc/grpc-js/src/client-interceptors.ts:454:34)
at Object.onReceiveStatus (/opt/app/node_modules/@grpc/grpc-js/src/client-interceptors.ts:416:48)
at /opt/app/node_modules/@grpc/grpc-js/src/resolving-call.ts:111:24
at processTicksAndRejections (node:internal/process/task_queues:77:11)
for call at
at ServiceClientImpl.makeUnaryRequest (/opt/app/node_modules/@grpc/grpc-js/src/client.ts:326:42)
at ServiceClientImpl. (/opt/app/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
at /opt/app/node_modules/dd-trace/packages/datadog-instrumentations/src/grpc/client.js:159:27
at run (node:diagnostics_channel:154:14)
at AsyncResourceStorage.run (/opt/app/node_modules/dd-trace/packages/datadog-core/src/storage/async_resource.js:69:14)
at node:diagnostics_channel:91:18
at Channel.runStores (node:diagnostics_channel:163:12)
at callMethod (/opt/app/node_modules/dd-trace/packages/datadog-instrumentations/src/grpc/client.js:149:23)
at ServiceClientImpl.wrapped [as validateAddress] (/opt/app/node_modules/dd-trace/packages/datadog-instrumentations/src/grpc/client.js:96:12)
at /opt/app/node_modules/@googlemaps/addressvalidation/build/src/v1/address_validation_client.js:180:29
```

I believe the SDK should retry on this error.

#### Environment details

- which product (packages/*): @googlemaps/addressvalidation
- OS: debian
- Node.js version: 20.5.0
- npm version: using yarn v1
- google-cloud-node version:

#### Steps to reproduce

Unsure, this is happening in production very sporadically however I do believe handling this issue should be relatively easy on the client side.

Also your troubleshooting guide (https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/troubleshooting) is a 404 same for https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/faq etc