Driver exception escalation

Extracted from https://github.com/citrusframework/citrus-db/pull/42#discussion_r291943588
-------------------

When a SUT interacts with the driver and this interaction leads to an exception, it is hard not possible to identify this in a test case. Nor is it possible to make the exception transparent at all, das the exception is part of the SUTs log, which is not in scope of the Citrus test case, suite or general setup.

Therefore, I propose to escalate exceptions to and endpoint of the Citrus JDBC Server and then pass the exception into the test case, so that an issue during driver interaction is escalated to the test case through the JDBC Server.

BR,
Sven

Start by tracing how the Citrus JDBC Server handles driver interactions and how exceptions currently remain in the SUT log rather than reaching a Citrus test case. Review the discussion extracted from pull request 42 to identify the intended escalation boundary; done means driver exceptions are observable in the test case through the JDBC Server, with behavior covered by the relevant tests.

Written by the indexing model from the issue text.