NUL bytes in SQL statements leads to late errors

The way the jdbc driver handles un-escaped NUL bytes in a SQL statement means they are ostensibly converted to a C-style string and truncated at the NUL.

While it can be argued this is malformed input and user error, and fine as it is, the error messages are needlessly confusing, and it's possibly an unnecessary attack surface for SQL injections.

If it's true that un-escaped NUL bytes in queries are never valid, it may be preferable to validate the query in `DuckDBPreparedStatement`, which ought to be a very cheap operation.

## Steps to reproduce:

```java
try (var dbConn = DriverManager.getConnection("jdbc:duckdb:");
var stmt = dbConn.createStatement();
) {
stmt.execute("SELECT 'a\0b'");
}
catch (SQLException ex) {
ex.printStackTrace();
}
```

```
java.sql.SQLException: Parser Error: unterminated quoted string at or near "'a"
LINE 1: SELECT 'a
^
java.sql.SQLException: java.sql.SQLException: Parser Error: unterminated quoted string at or near "'a"
LINE 1: SELECT 'a
```

Inizia da DuckDBPreparedStatement e riproduci il problema usando l’esempio JDBC con un’istruzione SQL contenente un NUL byte. Determina come viene gestita l’istruzione prima del parsing; il lavoro è completato quando le query non valide contenenti NUL byte ricevono un errore chiaro e immediato, invece dell’errore troncato e fuorviante del parser mostrato qui.

Scritto dal modello di indicizzazione a partire dal testo della issue.