feat(dev): add container dev runner

[tejaskash]

Summary

• add a streamed ContainerDevRunner for Docker, Podman, and Finch builds
• validate build inputs, protect widened contexts with .dockerignore, and map protocol-specific loopback ports
• keep environment and build-argument values out of argv while explicitly cleaning up project-scoped containers
• cover runtime selection, command construction, validation, cancellation, cleanup, and failure sequencing with fake process tests

Stack

• depends on feat(dev): CodeZip dev runner and process lifecycle core #1883
• intentionally targets feat/dev-server-core; retarget to refactor after feat(dev): CodeZip dev runner and process lifecycle core #1883 merges
• handler wiring and AWS credential materialization remain out of scope

Verification

• bun test (1013 tests)
• bun test src/core/dev/ (30 tests)
• bun run typecheck
• bun run lint:check
• bun run format:check
• bun run build

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.82%. Comparing base (1e7de20) to head (072611d).
⚠️ Report is 1 commits behind head on refactor.

Additional details and impacted files

@@             Coverage Diff              @@
##           refactor    #1962      +/-   ##
============================================
+ Coverage     96.79%   96.82%   +0.02%     
============================================
  Files           306      307       +1     
  Lines         17051    17182     +131     
============================================
+ Hits          16505    16636     +131     
  Misses          546      546              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[notgitika]

can we sanitize underscores when creating the image name, docker has rules here like only 2 consecutive underscore (runtimename can have many).

[notgitika]

finch does not forward arbitrary env vars into its VM, so --build-arg KEY loses the value.

should probably be --build-arg KEY=value

[notgitika]

for docker specifically, build args and app env vars are passed into Docker’s own environment. names like DOCKER_HOST can change which Docker daemon is used so can we keep these values separate?

[notgitika]

while I was trying on my own system, it seems like this treats a failed finch build --help as an unavailable binary. it was installed but not initialized. It should instead suggest running finch vm init. this is also likely a bug in the current CLI but I would like to have it fixed here if possible!