refactor(flow): consume kit fuzzy matchers (TIN-2098)

[Jesssullivan]

Summary

• consume @tummycrypt/scheduling-kit/fuzzy for the bridge fuzzy/date/field matcher surfaces
• keep bridge compatibility re-export modules so existing internal imports do not churn
• remove duplicated bridge scorer implementations and make kit scoreLabel the confidence authority for service token/fuzzy resolution
• bump the bridge kit edge to tummycrypt_scheduling_kit 0.9.2 / @tummycrypt/scheduling-kit ^0.9.2

Release / Registry Preconditions

• kit fuzzy implementation merged in feat(fuzzy): graduate matcher scorers to kit (TIN-2098) scheduling-kit#109 at 220a378e641e14587322836fd35a2a8a75fb2a8e
• kit release PR release: bump scheduling-kit to 0.9.2 scheduling-kit#110 merged at c59c610ba5f175a6d14f6cce1be67dcb35543ad1
• kit tag/release v0.9.2 published through workflow run 27498712471
• GHP @jesssullivan/scheduling-kit@0.9.2 verified from the package API
• registry PR feat(registry): register tummycrypt_scheduling_kit 0.9.2 tinyland-inc/bazel-registry#63 merged at ce0f399f17baaca90771f5e2d3d544988d52cd0e

Validation

• bazel build --registry=file:///private/tmp/kit092-registry-kwg2Oa/registry --registry=https://bcr.bazel.build //:typecheck
• bazel test --registry=file:///private/tmp/kit092-registry-kwg2Oa/registry --registry=https://bcr.bazel.build //:test
• bazel build --registry=file:///private/tmp/kit092-registry-kwg2Oa/registry --registry=https://bcr.bazel.build //:pkg
• bazel build --lockfile_mode=refresh //:typecheck
• bazel test //:test
• bazel build //:pkg

The first proof used the staged registry entry before merge; the second proof resolved 0.9.2 from the live registry with no local override.