feat(studio): show deployment progress and cloud build logs

[evanlowe]

Studio deployments become silent after printing the archive size, leaving users without feedback during upload, image building, and cloud release. Deployment progress now stays visible for both Volcengine and BytePlus, including the standalone scheduler scanner and worker Functions.

• Uploads display a progress bar, percentage, uploaded/total size, transfer speed, and ETA, with progress reset on retry and completion confirmed by the server response
• Application releases print new release logs and available linked build output, plus the region, revision, reported stage, elapsed time, and final URL
• Scanner and worker deployments identify each Function and console link, stream dependency installation logs, report release status and failed-instance logs, and confirm minute timer configuration
• Scheduler deployments report the current stage and elapsed time about every 15 seconds during quiet periods, including while a synchronous SDK request is pending; the heartbeat stops on completion, failure, or interruption
• Log snapshots are deduplicated, downloads are bounded, and optional log requests use short timeouts without interrupting deployment; credentials and signed URL queries are redacted

Existing upload payloads, Content-Length, mutation timeouts, and retry limits are preserved, with no new dependencies.

Sandbox environment builds also save logs and initial tool state before provisioning starts, and recheck persisted state before resuming provisioning. This prevents delayed writes from reverting a ready tool to creating and stale status polls from provisioning it again on either provider.

Validation:

• 220 local tests passed across environment builds, scheduler deployment, upload/release progress, and cloud integration
• Six deterministic regression cases failed before the fix and passed after it, covering delayed log writes on both sandbox presets and stale status polls for Volcengine and BytePlus
• Pre-commit checks passed, including Ruff and secret scanning
• Pyright passed for the changed environment service; the environment test file has the same 21 pre-existing type diagnostics as the baseline, with no additions
• Live cloud deployment remains a manual verification step