chore(deps): adopt @query-doctor/core ^0.23.0

[veksen]

Goal

Get the analyzer onto the core it needs to dump a schema correctly. Follows Query-Doctor/Site#3925, which published @query-doctor/core@0.23.0. This is the last step; nothing else is waiting on it.

What

Before: on 0.22.0, dumpSchema runs SQL whose CASE con.contype resolves to the char type, so every constraint name is cut to its first character. primary_key is dumped as p and foreign_key as f. Any consumer matching on the full name sees nothing.

After: constraint names arrive whole.

How

The range moves from ^0.22.0 to ^0.23.0, and the lockfile follows. No source changes.

0.23.0 also maps the old one-character codes back to names when it parses a snapshot, so schemas dumped by an analyzer still on 0.22.0 keep reading correctly. That is what makes this bump safe to land on its own schedule rather than in lockstep with anything.

Tests

No behavior in this repo changed, so no test was added. npm test passes locally against 0.23.0: 440 tests across 43 files, including the runs that dump a real Postgres schema in a container. tsc --noEmit is clean.

[github-actions]

Query Doctor — 6 successful checks

 Cost regression — No query went up more than 5%
 Untested data access — No changed data-access file without a test
 New query — No new queries
 New query with index recommendation — No new query ships an index recommendation
 Schema drift — No schema changes
 High-value nudge — No index or rewrite past the threshold

---

_{More details via MCP → get_ci_run({ runId: "019fdc56-9f17-7e4b-96d4-3bfa35bff20b" }) · view run · docs
3 queries read against main on assumed statistics of 10,000,000 rows per table. Sync production stats for costs measured against your real data.}