fix(cli): preserve release during setup refresh

[alongubkin]

Summary

• reconstruct setup release state after acquiring the deployment lock
• preserve the current release while using desired-or-current as the setup target
• avoid erasing hosted release authority during setup refresh handoff

Test

• cargo test -p alien-deploy-cli commands::up::tests -- --nocapture

[greptile-apps]

Greptile Summary

This PR reconstructs current and target release state after acquiring the deployment lock and ensures setup-preparation failures release that lock.

• Loads the current release and the desired-or-current setup target from lock-protected deployment state.
• Reuses one fetched release when current and target release IDs match.
• Wraps post-acquisition setup work so early errors release the deployment before returning.
• Adds tests for preserving the current release and selecting or reusing the target release.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
crates/alien-deploy-cli/src/commands/up.rs	Reconstructs release state under the acquired lock and adds mutually exclusive cleanup paths that release the deployment once on both preparation failure and normal completion.

Sequence Diagram

sequenceDiagram
    participant CLI
    participant Manager
    CLI->>Manager: Acquire deployment lock
    Manager-->>CLI: Lock-protected deployment state
    CLI->>Manager: Fetch current release
    opt Desired release differs from current
        CLI->>Manager: Fetch desired release
    end
    alt Setup preparation fails
        CLI->>Manager: Release deployment lock
        CLI-->>CLI: Return error
    else Setup attempt completes
        CLI->>Manager: Final reconcile
        CLI->>Manager: Release deployment lock
    end

Loading

_{Reviews (2): Last reviewed commit: "fix(cli): release setup lease on prepara..." | Re-trigger Greptile}