[SPARK-49730][SQL] classify syntax errors for pgsql, mysql, sqlserver and h2

[milastdbx]

What changes were proposed in this pull request?

In this PR I propose that we add classification of JDBC driver exception that represent syntax errors on external databases.
Queries generated from Spark that are sent to connectors should never have syntax error, and always indicate to a bug in code.

Having this classification would greatly help in identifying bugs faster and improving quality.

Documentation about error codes for syntax errors:
https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors-0-to-999?view=sql-server-ver16
https://www.postgresql.org/docs/current/errcodes-appendix.html
https://mariadb.com/kb/en/mariadb-error-code-reference/
https://www.h2database.com/javadoc/org/h2/api/ErrorCode.html

Why are the changes needed?

1. This gives customer more precise error message about issue being hit.
2. Help identify bugs faster as syntax error thrown from jdbc connectors should never happen.

Does this PR introduce any user-facing change?

Yes, previously customers would get FAILED_JDBC. UNCLASSIFIED or internal error when syntax error occurs in JDBC, whereas they will now get FAILED_JDBC.SYNTAX_ERROR

How was this patch tested?

Integration tests

Was this patch authored or co-authored using generative AI tooling?

No

[MaxGekk]

@milastdbx Could you have a look at the failed integration tests. Most of the failures are related to your changes, it seems.