fix: remote allocate/release fixes

[gmegidish]

Summary

• remote allocate --name now accepts a single value instead of requiring repeated flags.
• Device allocate/release now goes through the sessions REST API instead of the fleet.allocate/fleet.release WebSocket RPCs, so allocations are tied to a session from the start and can be looked up via GET /api/v1/sessions.

Changes

• commands/remote.go: FleetAllocateCommand creates a session (POST /api/v1/sessions) then allocates a device into it (POST /api/v1/sessions/{id}/devices). FleetReleaseCommand looks up the owning session by paging GET /api/v1/sessions and releases via POST /api/v1/sessions/{id}/devices/{deviceId}/release.
• rpc/rest.go (new): RESTCall helper for authenticated REST calls against the fleet server, deriving the HTTPS base URL from MOBILECLI_FLEET_URL.
• commands/remote_test.go, rpc/rest_test.go: tests covering the new allocate/release flow (session creation, pagination while searching for the owning session, error cases) and the REST client.

Testing

• go build ./...
• go test ./commands/... ./rpc/...

Related Issues

None

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c155fdcb-393b-47f8-8ce2-0a9d50b6a37a

📥 Commits

Reviewing files that changed from the base of the PR and between f937ee5 and 313981b.

📒 Files selected for processing (8)

• cli/filters.go
• cli/filters_test.go
• cli/flags.go
• cli/remote.go
• commands/remote.go
• commands/remote_test.go
• rpc/rest.go
• rpc/rest_test.go

---

_{Comment @coderabbitai help to get the list of available commands.}