[CRISvsGAME]

Fix data type case formatting when a CREATE TABLE column name is also a known keyword.

For example:

CREATE TABLE accounts (
    password VARCHAR(255),
    type VARCHAR(255)
);

With the default lowercase type case, the data types were left unchanged because the preceding column names were still recognized as keywords during type formatting.

The fix preserves the column context while processing the following recognized data type, without weakening keyword or type detection globally. It applies generically to data types handled by pgFormatter's existing type detection rather than to any specific type such as VARCHAR.

Regression coverage includes:

• keyword column names with VARCHAR
• SET type suppression with DOUBLE PRECISION
• DATE followed by a typed default as a control
• constraint names that are also type names as a control
• CREATE UNLOGGED TABLE
• uppercase type-case formatting with UUID
• an existing owner INT fixture that exposed the same issue

Validation:

• prove -Ilib t/*.t — 96 tests passed
• perl t/regress_test.pl — 284 fixtures passed