AWS Athena Connector - Table names with dot

### Version Information

Server Version: v2.33.4-cloud.1
CLI Version (for CLI related issue):

### Environment

Cloud

### What is the current behaviour?

Tablenames including a dot are not parsed properly which leads to a failing graphql query.

We do have a dort because we are using a certain schema in Postgres.

### What is the expected behaviour?

Tablenames including a dort are parsed properly and don't lead the graphql query to fail.

### How to reproduce the issue?

I guess it is a bit tricky to reproduce it. Please mention if you have an easier way:

1. Use https://github.com/CloudbreakUS/simple-database-archival-solution with PostgreSQL
2. Connect Hasura to AWS Glue Database with the Athena connector
3. Track a table and query data

### Screenshots or Screencast

### Please provide any traces or logs that could help here.

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

Don't use tablenames with a dot inside. I could change the code at https://github.com/CloudbreakUS/simple-database-archival-solution to not use a dot for the tablename and with that it works.

### Keywords

* AWS Athena

Start by reproducing the issue with the linked simple-database-archival-solution, PostgreSQL, AWS Glue Database, and the Athena connector. Track a table whose name contains a dot and query it through GraphQL; done means the table name is parsed correctly and the query succeeds without requiring a workaround.

Written by the indexing model from the issue text.