feat(sdk): regenerate vendored SDK to the 1.6.0 API surface (#150)

[brandonrc]

Summary

Phase 0 of the CLI 1.6.0 epic (#149): regenerate the vendored SDK against the Artifact Keeper v1.6.0 OpenAPI spec, fix the resulting drift, drop the #98 spec-fidelity workarounds, and bump the version to 1.6.0. This is the foundation the feature PRs build on, so it compiles and tests clean.

SDK regeneration

• sdk/src/generated_sdk.rs was rewritten by cargo run -p xtask -- generate from the v1.6.0 openapi.json. The large generated-file diff is the SDK regen (progenitor output, // This file is generated ... Do not edit.), not hand edits.
• New operation tag: re-exported ClientProjectsExt in sdk/src/lib.rs (the only new Client*Ext trait; all other 37 tags unchanged). No new top-level types needed beyond the whole-module types re-export.
• SDK crate version tracks the API at 1.6.0.

Drift fixed (new 1.6.0 request fields, all optional)

• CreateRepositoryRequest / UpdateRepositoryRequest gained 12 optional fields (apt_*, custom_user_agent, debian, npm_*, project_id, trusted_gpg_key, versioning_enabled) — set to None in repo.rs (CLI flags for these land in follow-up feature PRs).
• CreateSamlConfigRequest / UpdateSamlConfigRequest / SamlConfigResponse gained map_groups_to_groups — threaded through sso.rs (None in request builders, false in the test fixture).
• Test fixtures updated for new required response fields: RepositoryResponse now requires has_trusted_gpg_key + versioning_enabled; SamlConfigResponse requires map_groups_to_groups. Accepted the repo_show_json insta snapshot (adds the two new fields to JSON output).

#98 workarounds — dropped (spec now correct)

Verified against the v1.6.0 spec, then switched from raw HTTP to the strict generated SDK methods:

Workaround	Spec evidence (v1.6.0)	Action
service_account.rs create (200-vs-201)	POST /api/v1/service-accounts declares 201	Dropped → create_service_account(); updated the old handler_create_accepts_200 test to handler_create_rejects_non_201
email_subscriptions.rs subscribe (201)	POST /api/v1/repositories/{key}/email-subscriptions declares 201	Dropped → create_subscription(); test mock now returns 201
lifecycle.rs update PATCH (schema rename)	PATCH /api/v1/admin/lifecycle/{id} body is now UpdateLifecyclePolicyRequest (with priority), returns 200	Dropped → update_lifecycle_policy()

Kept (out of scope by design)

• artifact.rs single_put_upload raw PUT (streaming body — progenitor can't model it) and all chunked/multipart raw paths in chunked_upload.rs / import.rs / admin.rs (xtask strips multipart endpoints).
• lifecycle.rs create_policy raw POST — separate justification (backend CreatePolicyRequest shape), not a Backend/OpenAPI success-status mismatch (200 vs 201) breaks the strict SDK on create endpoints (artifact push, service-account create, ...) #98 item.

Verification (matches CI: .github/workflows/ci.yml)

• cargo check --workspace — pass
• cargo build --workspace — pass
• cargo fmt --all -- --check — pass
• cargo clippy --workspace -- -D warnings — pass (the exact CI clippy invocation)
• cargo test --workspace — 2024 passed, 0 failed

Note: cargo clippy --all-targets surfaces pre-existing warnings in test-only code (e.g. empty_line_after_doc_comments, dead-code in tests/common) that exist on main and are not part of the CI clippy gate (CI runs without --all-targets); no new warnings are introduced by this change.

Closes #150
Refs #149

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud