[BUG] Investigate Error Handling for unhandled SQL query

## Environment
- DocumentDB JDBC driver version: 1.4.4
- DocumentDB server version: n/a
- OS: [e.g. MacOS Big Sur 11.5.1, Windows 10 64-bit] n/a
- BI Tool or client name: n/a
- BI Tool or client version: n/a
- Java version (if known): n/a

---

## Problem Description
1. Steps to reproduce:
- In `DocumentDbQueryMappingService` original exceptions can be hidden on call to `getExceptionMessages(e)` - for example, if it throws a null pointer exception, hiding the original exception. This should be adjusted to ensure that the original error is preserved, and other error handling should be investigated to look for similar issues.
3. Expected behaviour:
4. Actual behaviour:
5. Error message/stack trace:
6. Any other details that can be helpful:

---

## Screenshots
- If applicable, add screenshots to help explain your problem.

---

## JDBC log
- Add related JDBC log entries here.

Locate DocumentDbQueryMappingService and inspect how getExceptionMessages(e) handles failures during SQL query processing. Trace the surrounding error-handling paths for similar cases. Done means the original exception is preserved and comparable handling issues are identified or addressed; the issue names no test file or specific test command.

Written by the indexing model from the issue text.