fix: rewrite docker-compose (legacy hyphenated CLI) to rtk docker compose

[slice-mihird]

Problem

Users on the legacy docker-compose CLI (hyphenated, v1) get 0% savings — the rewrite registry only handles docker compose (space-separated, v2). From rtk discover on a real machine, 40+ runs of docker-compose logs are fully missed.

Solution

Add a PATTERN and RtkRule for docker-compose that maps supported subcommands to rtk docker compose:

Command	Rewrites to
docker-compose ps	rtk docker compose ps
docker-compose logs [service]	rtk docker compose logs [service]
docker-compose build [service]	rtk docker compose build [service]
docker-compose up	(not rewritten — passthrough)
docker-compose down	(not rewritten — passthrough)

The filter code in container.rs already handles all three supported subcommands — this PR only adds the missing rewrite routing.

Changes

• src/discover/rules.rs: new pattern + RtkRule for docker-compose
• src/discover/registry.rs: 6 tests (3 supported, 3 skipped)

Testing

All 6 new tests cover the supported/skipped split:

test_rewrite_docker_compose_legacy_ps         ✓
test_rewrite_docker_compose_legacy_logs       ✓
test_rewrite_docker_compose_legacy_logs_no_service ✓
test_rewrite_docker_compose_legacy_build      ✓
test_rewrite_docker_compose_legacy_up_skipped ✓
test_rewrite_docker_compose_legacy_down_skipped ✓

Relates to #578.

🤖 Generated with Claude Code

[pszymkowiak]

Please retarget this PR to develop instead of master. We use develop as the integration branch — master is for releases only. You can change the base branch in the PR settings. Thanks!

[slice-mihird]

Done — retargeted to develop. Apologies for the wrong base!