feat: server-side cp/mv and new objects set-access command

[designcode]

Closes TIG-8731.

Summary

Adopt the new @tigrisdata/storage primitives (copy, move, setObjectAccess) so the CLI no longer streams object bytes through the client for remote↔remote operations. Same-bucket mv becomes metadata-only via X-Tigris-Rename: true; cross-bucket cp/mv use server-side CopyObject.

Changes

• tigris cp (remote→remote) — one copy(src, dest, { srcBucket, destBucket }) call replaces the prior head + get + put flow. Server-side CopyObject, no client traffic, source metadata preserved.
• tigris mv (remote→remote) — split:
  • Same-bucket → move(...) (metadata-only rename, one round-trip).
  • Cross-bucket → copy(...) + remove(...) (server-side, no client traffic). The server doesn't support cross-bucket move atomically; the SDK enforces this.
• New tigris objects set-access <bucket> <key> --access command using setObjectAccess. Dedicated home for the ACL operation that was previously mixed into objects set.
• tigris objects set marked deprecated: true with an onDeprecated message redirecting to tigris objects set-access (ACL) and tigris mv (rename). Implementation switched off the SDK-deprecated updateObject to move + setObjectAccess.
• Folder marker semantics preserved — zero-byte objects ending in / continue to use the put('') + remove() branch in both cp and mv (CopyObject on trailing-slash keys is ambiguous across S3 implementations).

Acceptance criteria (TIG-8731)

• Same-bucket tigris mv is metadata-only (no bytes through client).
• Cross-bucket tigris mv uses server-side copy + remove (no bytes through client).
• Same fix applied to cp.ts cross-bucket path.
• Folder-marker semantics preserved.
• mv -r parallelism (default 32) — follow-up PR, independent CLI work.
• --json per-key failure reporting — follow-up PR, same loops.

Test plan

• npm run lint and npm run format:check pass
• npm test passes (659 unit / spec tests)
• npm run build succeeds
• Integration tests added:
  • Cross-bucket cp keeps source, creates destination
  • Cross-bucket mv removes source, creates destination
  • objects set-access --access public/private succeeds
  • objects set-access without --access exits non-zero

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes core cp/mv object-transfer behavior to rely on new server-side storage primitives, which could affect data movement semantics (especially cross-bucket moves and folder markers) if the SDK/server behavior differs from the previous stream-based implementation.

Overview
Switches remote→remote cp and mv to use new @tigrisdata/storage server-side primitives so object bytes no longer stream through the CLI. cp now uses copy() (with a put('') fallback for folder markers), and mv uses move() for same-bucket renames and copy() + remove() for cross-bucket moves.

Adds a new objects set-access command backed by setObjectAccess, and marks objects set as deprecated in specs.yaml; objects set is reimplemented to rename via move() first (when --new-key is provided) and then update ACL via setObjectAccess.

Bumps @tigrisdata/storage to ^3.5.1 and extends integration coverage with cross-bucket cp/mv and objects set-access tests.

^{Reviewed by Cursor Bugbot for commit 7e124e7. Bugbot is set up for automated code reviews on this repo. Configure here.}