feat(fuzzy): graduate matcher scorers to kit (TIN-2098)

[Jesssullivan]

Summary

TIN-2098 kit-side extraction: publish the bridge fuzzy-in scorer/matcher machinery as a backend-agnostic kit subpath.

• Adds @tummycrypt/scheduling-kit/fuzzy with the shared scorer cascade (normalize, token overlap, Levenshtein confidence, scoreLabel).
• Adds ServiceMatcher, DateMatcher, and FieldMatcher machinery with Effect Context tags under scheduling-kit/*.
• Adds the bridge-derived property suites to kit unit coverage: confidence bounds, threshold monotonicity, cascade ordering, slot membership, month parsing, and field-rule inference.
• Exports the subpath through package.json and re-exports it from the root kit surface.
• Extends the unit-test include list so src/fuzzy/__tests__ is covered by default pnpm test:unit.

This is pure extraction: no browser automation, no Acuity DOM code, no app-specific deployment logic.

Validation

• pnpm exec svelte-kit sync && pnpm exec vitest run src/fuzzy/__tests__ --reporter=verbose — 49 passed
• pnpm check — 0 errors / 0 warnings
• pnpm test:unit — 814 passed (30 files)
• pnpm build — emitted dist/fuzzy/*
• pnpm exec publint — All good
• pnpm lint — clean
• pnpm check:release-metadata — aligned for 0.9.1
• bazel build //:pkg — passed
• git diff --check — clean

Notes

I intentionally did not add a new fine-grained //:fuzzy Bazel target in this PR. The repo's existing standalone ts_project pattern currently conflicts with the SvelteKit-generated tsconfig/noEmit setup; //:pkg remains the canonical package artifact and passes.

Refs TIN-2098.