fix(replay): unbreak the capture/replay harness (lk resolution + env-name refresh)

[cathysnell]

Problem

The replay/capture launchers cannot run on current main. A fresh
capture-scenario.sh --create (and the replay/smoke launchers, which share the
same resolver) hard-fails at the first pre-project lk call:

bash: .../templates/project/common/scripts/lk: No such file or directory
capture-scenario: kit --warm failed

KIT_LK still points at templates/project/common/scripts/lk, a shim that was
removed from this repo — the scaffold lk now lives in the
@databricks-solutions/lakebase-scm-utils substrate package (see the header of
examples/replay/lk) and was made generic, so it needs LAKEBASE_KIT_PACKAGE
to know which kit to load. This is very likely why the shipped stockflow corpus
is still a v0.3.0-beta.14 recording: the capture path is broken, so it cannot be
re-recorded.

Fix

1. lk resolution. Resolve KIT_LK via a shared kit_lk_path() helper in
   lib/pin-local-kit.sh (installed substrate path, with the legacy in-repo path
   as a fallback), and export LAKEBASE_KIT_PACKAGE from
   resolve_kit_single_source so the generic shim resolves the kit for the
   pre-project --warm / lakebase-create-project calls. A scaffolded project
   reads .lakebase/kit-package, but the launchers invoke lk before any project
   exists. Applied to capture-scenario.sh, _replay-smoke.sh, run-smoke.sh.

2. Env-name refresh. Rename the deprecated LAKEBASE_SFTDD_{AUTO_CONTINUE,SPRINT_REQUESTS}
   to the current LAKEBASE_CONSORT_* prefix across the active launchers + docs.
   consortEnv() reads CONSORT_* first (SFTDD/TDD remain fallbacks), so this
   is behavior-preserving on the current engine; it silences the per-capture
   deprecation warnings and won't break at the scheduled v0.4.0 removal.

Tests

• New hermetic anti-drift guard in replay-layout-guard.test.ts: the launchers
  must resolve KIT_LK via kit_lk_path (not the removed in-repo path), and
  pin-local-kit.sh must define the helper + export LAKEBASE_KIT_PACKAGE.
• Updated the two guards that pinned the old state (npx-tax-guard.test.ts was
  asserting the removed lk path; consort-workflow-smoke.test.ts asserted the
  old env name).
• npm run typecheck clean; the affected hermetic suites pass. Verified the fix
  end-to-end: with the patched resolver, lk resolves the pinned kit and
  lakebase-create-project runs, and a live capture-scenario.sh --create
  provisions + drives past setup.

Notes for maintainers

• Scope is the replay harness only; no engine/kit runtime code changes.
• Heads-up (separate from this PR): running the full npm test inside a
  linked git worktree corrupts the worktree's git — several build-lane tests
  (cycle-record, greenOpenCycle, cutExperiment, …) make real git commits
  that land on the current branch instead of an isolated fixture (branch HEAD gets
  rewritten with green: T1/T2 / refactor commits). Worth isolating those
  tests' git ops; happy to file/fix separately.

This pull request and its description were written by Isaac.