Use idiomatic Effect primitives in config and SSH readiness

[cursor]

What Changed

• Switched SSH tunnel readiness timing options/constants from raw millisecond numbers to Duration values, while only converting to milliseconds at remote-script/log boundaries.
• Reworked VCS project config loading to decode JSON with Schema.fromJsonString and model missing/invalid values with Option.
• Added coverage for invalid VCS project config JSON fallback behavior.

Why

This keeps Effect-based code closer to Effect primitives, makes timing policy easier to test with Effect clocks, and removes ad-hoc JSON.parse/null handling from VCS config parsing.

UI Changes

Not applicable.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

  

Note

Replace numeric millisecond values with Effect Duration primitives in SSH tunnel and VCS config

• Replaces raw millisecond numbers with Duration-typed constants and parameters in tunnel.ts; callers must now pass Duration values for timeout, interval, and probeTimeout to waitForHttpReady.
• Rewrites VcsProjectConfig helpers in VcsProjectConfig.ts to use Option instead of nulls and try/catch, including findConfigPath, parseConfig, and readConfiguredKind.
• Adds a test case for malformed VCS config JSON, asserting resolveKind returns 'auto'.
• Behavioral Change: waitForHttpReady now uses an outer Effect.timeoutOption to bound total duration instead of a fixed retry count, and readConfiguredKind returns 'auto' on any parse failure with a warning log.

^{Macroscope summarized 6dfcdaa.}