fix: keep getQuerySource out of getRecentQueries after reset

[veksen]

Summary

• The non-default-schema reset test (resetPgStatStatements works with a non-default schema) was failing with expected 1 to deeply equal +0 — one query survived pg_stat_statements_reset().
• Root cause: getQuerySource() had no @qd_introspection marker AND its IN-list literals normalize to $1, $2, so neither filter in getRecentQueries() caught it.
• Adding -- @qd_introspection after the trailing ; didn't help: Postgres strips trailing comments past ; from the text pg_stat_statements stores (verified empirically). Moved the marker before the terminator so it actually survives.

Test plan

• npx vitest run src/sync/pg-connector.test.ts — all 7 tests pass locally against postgres:17
• Re-run the CI Release Action job and confirm it gets past this test

[github-actions]

Query Doctor Analysis

View full run details

2 queries analyzed

2 pre-existing issues

• SELECT "guests"."id", "guests"."session_id", "guests"."username", "guests"."avatar_path", "guests"."color", "guests"."side", "guests"."audio_recording_path", "guests"."audio_recording_public", "gue...
  index assets(event_id, inserted_at desc)
  cost 31,003,449 → 1,498 (100% reduction)
• SELECT * FROM guest_ip_addresses WHERE ip_address = '127.0.0.1';
  index guest_ip_addresses(ip_address)
  cost 154,402 → 8 (100% reduction)

_{Using assumed statistics (10000000 rows/table). For better results, sync production stats.}