fix: EXPOSED-695 DDL for unnamed check constraints fails when table has schema name

[bog-walk]

Description

Summary of the change:
Check constraints created without user-specified names now use full table name with any dot-prefixed schema name replaced with underscores.

Detailed description:

• Why:

A schema-prefixed table name currently uses the full name (with dot character) when generating a name for unnamed check constraints. This results in syntax exceptions or schema-not-found exceptions because something like this Table("my_schema.my_table") will name the constraint check_my_schema.my_table_index_1.

• How:
  • Move common unquoting and . character replacement logic to private Table properties
  • Use above logic when generating constraint name instead of raw tableName
  • These constraints will be named like check_my_schema_my_table_index_1 to match pattern used when naming implicit column constraints.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix

Affected databases:

• All

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

EXPOSED-695