Read metadata from remote Exasol

[redcatbear]

Situation

In the first MVP of the Exasol Virtual Schema we only supported reading metadata from a local Exasol database. The first step in enabling access to a remote Exasol database is to be able to read the metadata using the Lua Exasol Driver.

Acceptance Criteria

1. Users can define a remote connection
2. Exasol can read the metadata for a remote connection
3. An integration test proves that reading the remote metadata works
4. Properties are backward-compatible (ignoring is OK) with the existing Java-variant
5. Connection definitions are backward-compatible with the existing Java-variant

It is okay though if the test accesses the same database as long as it uses the database driver to do it. Since IMPORT is not in the scope of this ticket, this kind of test is the easiest way to decouple the tickets.

Implementation hints

Check "Accessing Connection Definitions" in the online handbook for details on how to read the contents of connection definitions in a Lua script.