fix: migrate discos-cli to current EvidenceOS protocol

[jverdicc]

Motivation

• Discos CLI was failing to compile due to EvidenceOS protocol and API drift; the daemon/client proto types and request/response shapes changed and must be adapted.
• Ensure the CLI remains compatible with the workspace evidenceos-protocol/evidenceos-core APIs and the new request/response field names so runtime and verification flows continue to work.

Description

• Added missing discos-cli dependencies: evidenceos-core and evidenceos-protocol in crates/discos-cli/Cargo.toml so protocol constants and safety_policy resolve against the workspace API.
• Updated CreateClaimV2Request call sites to include the new fields nullspec_id, dp_epsilon_budget, and dp_delta_budget, and converted epoch_size using .into() where appropriate; preserved dual-use policy logic and fixed borrowing/binding issues (ref cmd, cloning, and dereferencing) to avoid partial-move errors.
• Migrated commit flow to the new CommitArtifactsRequest shape by building a Vec<pb::Artifact> (mapping digest→artifact_hash, name→kind) and passing artifacts plus wasm_module in a single commit_artifacts RPC, and updated the CLI output to use the response state field.
• Adjusted fetch-capsule handling to the new response field names: etl_root_hash→root_hash, inclusion→inclusion_proof, consistency→consistency_proof, etl_tree_size→tree_size, sth_signature→signed_tree_head (extracting .signature), and capsule→capsule_bytes, and fixed conversions for proof node vectors and types.
• Updated Freeze output to use state instead of frozen and changed revocation watching to iterate WatchRevocationsResponse.entries and use the current entry fields (reason, timestamp_unix).
• Avoided requiring Serialize on the proto FeatureFlags by converting it to a stable printable JSON string via format!("{:?}", ...) when embedding in server JSON output.
• Minor formatting and ergonomics fixes (use args.log.clone() for env filter, adjust boolean/borrow dereferences) to make the changes build cleanly.

Testing

• Ran cargo check -p discos-cli and the check completed with no errors.
• Built the binary with cargo build -p discos-cli and it finished successfully (EXIT:0).
• Ran cargo check --workspace and it completed with no errors.
• Ran cargo fmt to apply formatting (an initial cargo fmt --check reported diffs), after which formatting checks passed.

---

Codex Task