Properly handle table existence check for jdbc dialects

[milastdbx]

What changes were proposed in this pull request?

In this PR, I propose that we rethrow exception when we are doing table existence check in jdbc dialect, if exception is not related to table not being found. I propose this because currently all exceptions get swallowed and method returns false. From the perspective of the system its as if table doesn't exist, which is a wrong message (e.g, we can get table does not exist if network to jdbc database is down).

This issue is mostly exposed when TableCatalog API is used,

  override def loadTable(ident: Identifier): Table = {
    if (!tableExists(ident)) {
      throw QueryCompilationErrors.noSuchTableError(ident)
    }

How its implemented today, tableExist cannot throw anything, so every exception gets converted to noSuchTableError which is wrong.

Does this PR introduce any user-facing change?

Customers will get proper error messages.

How was this patch tested?

Tests

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

Generetad by: COPILOT

[milastdbx]

I will create SPARK jira ticket shortly