Neon db URL with pooler issue on Hasura Metadata

### Version Information

Server Version: v2.29.1-cloud.1

### Environment

Cloud

### What is the current behaviour?

When connecting a neon.tech db with pooler (PGBouncer) I'm getting metadata errors status even if i disable the `Use Prepared Statements` option.

### What is the expected behaviour?

The neon database with pooler shouldn't cause issues with the right settings.

### How to reproduce the issue?

Use the pooled URL from a neon database and disable `Use Prepared Statements`.
Seems related to #7741

### Screenshots or Screencast
```json
{
"statement": "BEGIN ISOLATION LEVEL READ COMMITTED READ ONLY",
"prepared": true,
"error": {
"exec_status": "FatalError",
"hint": null,
"message": "prepared statement \"0\" already exists",
"status_code": "42P05",
"description": null
},
"arguments": []
}
```

### Any possible solutions/workarounds you're aware of?

Use the neon db URL without pooler

### Other remarks

There is no clear indication in Neon or Hasura documentation if it's preferable performance wise to use the native hasura pooler or an external one [as described here](https://github.com/hasura/graphql-engine/issues/7741#issuecomment-961185775)