Quote PostgreSQL schema/table identifiers in metadata-derived SQL names

[Copilot]

PostgreSQL queries failed for schemas starting with numeric characters (e.g. 0HEM8B0GQNB5M) because metadata extraction produced unquoted schema.table names. This caused invalid SQL parsing (trailing junk after numeric literal) when those names were used in generated queries.

• Identifier rendering fix (PostgreSQL metadata path)

  • Updated PostgreSQLDataExclusion to build DbTable.fullName with quoted identifiers for both schema and table.
  • Added identifier escaping for embedded double quotes to keep generated names SQL-safe.

• Behavioral impact

  • Generated table references now follow PostgreSQL quoted-identifier rules, including numeric-leading schema names and case-sensitive identifiers.

• Focused regression coverage

  • Added a unit test in PostgreSQLDataExclusionTest validating that schema 0HEM8B0GQNB5M and table t_region produce a fully-qualified name as quoted identifiers.
  • Added a unicode identifier test in PostgreSQLDataExclusionTest validating quoted full-name generation for unicode schema/table names (e.g. "dátá_数据"."dátá").

// Before
fullName = schemaName + "." + metaDataTable.tableName();

// After
fullName = getQuotedName(schemaName) + "." + getQuotedName(metaDataTable.tableName());
// => "0HEM8B0GQNB5M"."t_region"

[thadguidry]

@copilot can you add a new issue so that we ensure we have similar test and handling for table and schema names for mysql and it's convention use of backticks?

In this pr, I'd like you to also add to the test case for unicode in table or schema names. Example:
-- Equivalent to "data"
U&"d\0061t+000061"

[Copilot]

@copilot can you add a new issue so that we ensure we have similar test and handling for table and schema names for mysql and it's convention use of backticks?

In this pr, I'd like you to also add to...

Added unicode identifier coverage to the PostgreSQL test in commit c78a73c (shouldQuoteUnicodeSchemaAndTableNameInFullName). I’m unable to create a new GitHub issue from this environment because GitHub CLI auth is unavailable here; please open a follow-up issue for MySQL backtick schema/table handling and I can implement it next.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh gh auth status -h github.com (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[thadguidry]

@kdhrubo are you satisfied on this changes and ready to merge?