fix(parse): check INSERT columns and UPDATE SET targets in strict mode

[tiagolauer]

Fixes #282.

The bug

StrictRow<DB, 'insert into users (naem) values ($1)'>       // Record<string, never> - no error
StrictRow<DB, 'update users set naem = $1 where id = 1'>    // same

Both are guaranteed runtime errors on every engine. The documented list of unchecked clauses covers GROUP BY, HAVING and ORDER BY; column names in write statements are not on it, and no test pinned this either way.

The fix

Nothing scanned the SET assignment targets or the INSERT column list against the schema — the DML branches used those lists only to position placeholders for params inference.

The parsed statement now carries the write column text (INSERT's list, or UPDATE's SET targets), and the row check resolves each name through the same ResolveColumnType that RETURNING columns go through, so the message is identical to the one every other path produces.

Shapes it cannot read are left alone rather than guessed at:

• a row assignment (set (a, b) = (1, 2))
• an INSERT with no column list
• anything whose target is not a plain name

Budget

MAX_INSTANTIATIONS moves 200,000 → 210,000, raised in this commit as the script asks.

	instantiations
master	192,486
naive (structural row test first)	204,196
gated on the column text first	201,322

A SELECT carries an empty string here and pays only for that; the ~4.5% is the two clause scans a write now runs (SplitAtTopLevelKeyword for VALUES/SELECT, and for SET) plus the extra field on the parsed statement.

Verification

tests/write-column-check.test-d.ts, twelve cases. Five red on master:

tests/write-column-check.test-d.ts(18,3): error TS2344: Type 'false' does not satisfy the constraint 'true'.
tests/write-column-check.test-d.ts(25,3): ... (32,3), (39,3), (46,3)

• unknown INSERT column, unknown SET target, each also when it is not the first entry, and an unknown INSERT column with a RETURNING that would otherwise have typed fine

Controls: valid writes (with and without RETURNING), an INSERT with no column list, a subquery on the value side of a SET, a qualified SET target, and loose mode.

tsc --noEmit clean, 192 runtime tests pass.