Add tests for large metadata

[mshustov]

to verify the client and JDBC driver handle cases with a couple of thousand tables. see metabase/metabase#52496

[chernser]

I'm a bit confused. Original issue says:
"As far as I understand, Metabase finds some table during the sync-tables task and can't find it during the sync-fields."
Ok - two phase sync.
Then to reproduce the issue:
"When the sync-tables task is completed, delete the new table as soon as possible"

• it looks like a Metabase issue. Driver returns information from database and has no schema cache. Metabase can implement it.
• what should we do with removed table?
• as I can see whole sync is failed, what make sense - do not change schema while schema sync. But again - error handling is on Metabase side.

[mshustov]

The root cause for this particular problem on the Metabase-side, my point was that we don't have some sort of a stress testing for the driver

[chernser]

@mshustov I agree that we need some stress tests.
But the issue with metabase is a different - they are affected by temp. tables or views. User just want metabase to ignore fact they are missing and continue sync. process.