Switch native query execution to use Statement instead of PreparedStatement (#14883)

Switch query execution to use `Statement` instead of `PreparedStatement` when there are no params

Add new multimethod to create a `Statement`, rather than `PreparedStatement`, which works similarly, called `statement`

Add new multimethod to run a SQL query against a Statement, similar to `execute-query!`, called `execute-statement!`

For consistency, rename `execute-query!` to `execute-prepared-statement!`

Change `execute-reducible-query` to capture whether the query has params, and if not, using the new multimethods instead

Update fetch-results-metadata-test so it replaces execute-select! instead of prepared-statement

Adding `statement-supported?` multimethod (defaults to true), to let drivers control whether statements are used at all

Updating Oracle driver to not override holdability for `statement`, similar to `prepared-statement`, and bumping module version

Updating SparkSQL driver to indicate that statements are not supported, and bumping module version

Fixing Redshift test to also override `execute-statement!` so it can capture the SQL for a statement