SqlParser can mark valid statements as invalid, preventing worker deployment

[whit0694]

PR #1619 added a utility to parse user-defined queries.

At least in Oracle it's possible to have valid queries that fail validation, preventing us from creating the Connect worker

We have queries that work, but that we can not run EXPLAIN on, due to ORA-01039 errors.

The owners of the underlying views aren't going to change things to allow us to run EXPLAIN, so we're unable to deploy the worker.

Could we have the SqlParser be optional? In the original PR the stated goal of implementing the parser was to help people that have query.masked enabled. We don't use that feature, so maybe we could skip parsing unless query.masked is enabled?

[whit0694]

Another example of this

I have a Connect Source worker that works fine under jdbc 10.9.2 when connecting to an AWS RDS Oracle DB. When I update to 10.9.3 I can no longer deploy the worker because the validation code throws

The configured query is not valid and has database/connection errors. Please provide the correct query by validating the query syntax and the existing table/column names with the database being connected

The query is fine, as is the connection.

[Muktha9491]

Hi, I'd like to take this issue. If it's available, could you please assign it to me?