Support both bun.lock and bun.lockb in package manager detection

Description

In both setup-ts-deep-modules and setup-pre-commit, package manager detection currently checks for bun.lockb exclusively:

• skills/in-progress/setup-ts-deep-modules/SKILL.md (Line 41)
• skills/misc/setup-pre-commit/SKILL.md (Line 19)

In modern versions of Bun (v1.2+ / v1.1.35+), Bun defaults to generating a text-based bun.lock instead of the legacy binary bun.lockb. As a result, agents running these skills on newer Bun projects will fail to recognize Bun as the project's package manager.

Proposed Fix

Update the detection in both skills to recognize either bun.lock or bun.lockb, preserving backwards compatibility with legacy projects while properly supporting modern Bun setups:

• In skills/in-progress/setup-ts-deep-modules/SKILL.md: - **Package manager**: \pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `bun.lock` or `bun.lockb` → bun, else npm.`
• In skills/misc/setup-pre-commit/SKILL.md: Check for \package-lock.json` (npm), `pnpm-lock.yaml` (pnpm), `yarn.lock` (yarn), `bun.lock` or `bun.lockb` (bun). Use whichever is present. Default to npm if unclear.`

Ready Diff

Since pull requests from external contributors are restricted in this repository, we have already prepared and tested the changes on a fork:

• Diff comparison: https://github.com/mattpocock/skills/compare/main...syx-labs:mattpocock-skills:fix/support-bun-lock
• Commit: https://github.com/syx-labs/mattpocock-skills/commit/8501c28b5a03bc5ff7e5a625b0f5ef5b8f62f3a6