Hasura Console Data Screen has Very Long Load Time with Large Amounts of DB Tables

### Is your proposal related to a problem?

While using a self-hosted Docker instance of Hasura, the Data screen in the Hasura Console seems to take 20 minutes to load in the tables of databases

with 100+ tables. It sometimes hangs indefinitely and never loads any tables, tracked or untracked. The GraphQL engine is still able to process queries from the large databases, but it has become difficult to track new tables or add new table relationships.

### Describe the solution you'd like
An update to the Hasura Console frontend so that it can handle large amounts of DB tables and is scalable to demand.

### Describe alternatives you've considered
I have tried manually updating Hasura Metadata JSON to track new tables and relationships, but I rather use the Hasura Console to do these tasks. Especially when I am introducing this product to less technical users.

Thank you!

Reproduce the issue in a self-hosted Docker instance with a database containing 100+ tables, then trace the Hasura Console Data screen's loading path. Done means the screen loads tracked and untracked tables reliably at this scale and still supports tracking tables and adding relationships.

Written by the indexing model from the issue text.