Make Tailscale Effect integration more idiomatic

[cursor]

What Changed

• Switched Tailscale timeout constants and APIs to effect/Duration inputs.
• Represented optional MagicDNS results with Option instead of null through the Tailscale parser and desktop endpoint provider.
• Converted Tailscale errors to Schema.TaggedErrorClass and updated tests to use Layer.mock plus TestClock for timeout coverage.

Why

This keeps the Tailscale integration aligned with idiomatic Effect patterns and makes timeout behavior deterministic in tests.

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 nullable strings with Option types in Tailscale Effect integration

• Converts magicDnsName fields across TailscaleStatus, parseTailscaleMagicDnsName, and resolveTailscaleHttpsBaseUrl from string | null to Option.Option<string>
• Replaces numeric millisecond timeout constants with Duration-based constants (TAILSCALE_STATUS_TIMEOUT, TAILSCALE_SERVE_TIMEOUT, TAILSCALE_PROBE_TIMEOUT) and updates runTailscaleCommand to accept timeout: Duration.Input instead of timeoutMs: number
• Migrates error classes (TailscaleCommandError, TailscaleStatusParseError, TailscaleUnavailableError) from Data.TaggedError to Schema.TaggedErrorClass with explicit field schemas
• Adds a timeout test using TestClock to verify readTailscaleStatus fails with TailscaleCommandError after TAILSCALE_STATUS_TIMEOUT
• Risk: probeTailscaleHttpsEndpoint callers passing timeoutMs will silently have no effect; the property is now timeout

^{Macroscope summarized df8b880.}