feat: add Bun and Deno runtime support

[bz00qa]

Summary

Add token-optimized filtering for Bun and Deno CLI commands, extending RTK's JavaScript/TypeScript runtime coverage.

Bun commands

• rtk bun install/add/remove — strip progress bars, version headers (~80% reduction)
• rtk bun test — failures only via runner (~90% reduction)
• rtk bun build — errors only via runner
• rtk bun run — passthrough (script output unpredictable)
• rtk bun pm ls — JSON parsing with sorted compact dependency tree
• rtk bunx <tool> — smart routing: tsc → tsc filter, eslint → lint filter, others → error filter

Deno commands

• rtk deno test — failures only via runner (~90% reduction)
• rtk deno lint/check — strip download lines, tee recovery on failure
• rtk deno run/task — passthrough with download line stripping
• rtk deno compile — errors only via runner
• rtk deno install — passthrough

Hook integration

• Added bun, bunx, deno patterns to discover registry (PATTERNS + RULES)
• Commands auto-rewritten by rtk rewrite hook
• Added to is_operational_command security whitelist

Files changed

• New: src/bun_cmd.rs (261 lines), src/deno_cmd.rs (254 lines)
• Modified: src/main.rs (mod declarations, Commands enum, subcommand enums, dispatch logic)
• Modified: src/discover/rules.rs (3 patterns + 3 rules)

Test plan

• 7 bun_cmd unit tests (install filtering, JSON parsing, text truncation, error preservation)
• 4 deno_cmd unit tests (download stripping, empty output, error preservation)
• All 898 existing tests pass (1 pre-existing binlog CRLF failure on Windows unrelated)
• cargo clippy — no new warnings
• cargo fmt — clean

🤖 Generated with Claude Code

[engels74]

Besides the Deno support, isn't the bun integration a duplicate of #453?

[Ffinnis]

Besides the Deno support, isn't the bun integration a duplicate of #453?

I think we can stay with this variant

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[aeppling]

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling