[REV-2383] Scope schedule operations to selected team

[warp-agent-staging]

Description

Scope oz schedule list and schedule creation to a validated personal or selected-team context. Both commands now refresh team metadata, mint RequestTeamScope, and send X-Warp-Team-Uid only for selected-team Warp Drive requests before reading scoped schedules or environments. Scoped refreshes submit only personal and selected-team versions and cannot evict personal or sibling-team cache entries. Owner resolution remains independent, and UID-addressed get/update/pause/unpause/delete behavior remains unchanged.

Built on parent PR #15805. The server-side active-team filter is in warpdotdev/warp-server#16853.

Origin: https://warpdev.slack.com/archives/C0BREN45G2D/p1788501775785069

Linked Issue

REV-2383

• The linked issue is labeled ready-to-spec or ready-to-implement.
• No screenshots or video apply; this is a headless CLI behavior change and computer-use verification was declined.

Testing

• cargo nextest run -p warp_cli -p warp -E 'test(schedule_) or test(team_scoped_graphql_request)' — 18 passed on the original vertical.

• Focused cargo test -p warp --lib regressions for request-scoped versions, scoped deletion safety, schedule visibility, and GraphQL team headers — 6 passed.

• ./script/format --check and ./script/check_no_inline_test_modules — passed.

• cargo clippy -p warp_server_client --all-targets --tests -- -D warnings — passed on the original vertical.

• cargo clippy -p warp_cli --all-targets --tests -- -D warnings — passed on the original vertical.

• cargo clippy -p warp --all-targets --tests -- -D warnings — passed after the cache-safety update.

• The workspace-unified Clippy stage could not complete because the dedicated 49 GB Cargo target filesystem was full (No space left on device); CI is pending on the pushed head.

• I have manually tested my changes locally with ./script/run — not run; automated CLI and request-transport tests cover this headless behavior.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-NONE

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-factory on this PR to send it follow-up work.