Support config-only redeploys for existing installations

[bermanto]

Problem

Existing terminal-installed deployments can retain stale generated Wrangler configuration after HQBase fixes deployment configuration. The signed-release deploy path exits early when the active version and release tag already match, so operators have no supported way to regenerate the deployment config and redeploy the same verified release.

This was split from #4. PR #6 fixes the generated configuration for new installations, but existing affected installations still need a safe recovery path.

Expected behavior

Provide a supported operation that:

• regenerates deployment configuration from the saved .hqbase/deployments/<name>/manifest.json and current verified release;
• redeploys without changing the signed release version or bypassing release verification;
• preserves Worker secrets and existing bindings;
• affects only resources recorded in the deployment manifest;
• verifies the resulting Worker and reports a clear no-op when configuration is already current.

Verification

Add tests for an existing installation with stale asset routing, successful config-only redeploy, preserved secrets/bindings, and an already-current no-op.