fix(odc): use double-quote identifier quoting for PG-family queryTableOrViewData

Previously the PG-family branch in ConnectConsoleService.queryTableOrViewData
reused MySQLSqlBuilder, which wraps identifiers with back-ticks (`schema`.`table`).
openGauss / GaussDB / PostgreSQL reject back-ticks and return SQLState=42601
syntax error at or near "`" when a user clicks the table 'Data' tab.

Switch the PG-family branch to OracleSqlBuilder, whose identifier() wraps with
ASCII double quotes ("schema"."table"), which is the canonical PostgreSQL
identifier-quoting style. Only identifier() / schemaPrefixIfNotBlank() are used
in this code path; OracleSqlBuilder's other Oracle-specific behaviors
(value quoting, default values, LIKE ESCAPE) are not invoked here, so the reuse
is safe.

Fixes actiontech/dms-ee#865

Author: LordofAvernus

server/odc-service/src/main/java/com/oceanbase/odc/service/session/ConnectConsoleService.java

@@ -185,10 +185,17 @@ public SqlExecuteResult queryTableOrViewData(@NotNull String sessionId,
             asyncExecuteReq.setFullLinkTraceEnabled(false);
             return executeQueryTableOrViewData(sessionId, connectionSession, asyncExecuteReq);
         } else if (dialectType.isPgFamily()) {
-            // GaussDB / openGauss use PostgreSQL wire protocol. MySQLSqlBuilder generates
-            // "SELECT t.* FROM schema.table t LIMIT n" which is valid PostgreSQL syntax,
-            // so it is reused here for PG-family dialects. This also covers POSTGRESQL.
-            sqlBuilder = new MySQLSqlBuilder();
+            // GaussDB / openGauss / PostgreSQL use PostgreSQL wire protocol, where identifiers
+            // are quoted with double quotes (e.g. "schema"."table"), NOT MySQL back-ticks.
+            // Reusing MySQLSqlBuilder here previously produced
+            // SELECT t.* FROM `schema`.`table` t LIMIT 1000
+            // which triggered SQLState=42601 syntax error at or near "`" against openGauss.
+            // OracleSqlBuilder.identifier() wraps identifiers with '"' (see
+            // StringUtils.ORACLE_IDENTIFIER_WRAP_CHAR), which is exactly what PG expects.
+            // Only identifier() / schemaPrefixIfNotBlank() are exercised below, so the rest of
+            // OracleSqlBuilder's Oracle-specific behavior (value quoting, default values,
+            // LIKE ESCAPE) is never invoked here and is therefore safe to reuse.
+            sqlBuilder = new OracleSqlBuilder();
         } else {
             throw new IllegalArgumentException("Unsupported dialect type, " + dialectType);
         }