chore: switch replay commands to SDK endpoints

[nieomylnieja]

Motivation

The related Go SDK change includes a versioned Replay API. Sloctl no longer needs separate Replay HTTP requests and models.

Summary

• Migrated Replay run, availability, status, list, cancel, and delete operations to sdk/endpoints/replay/v1.
• Preserved SLO handling across API versions and restored project scope when API responses omit metadata.project.
• Preserved source-SLO objective mappings and RFC3339 createdAt values in Replay list output.
• Used only the SLO selector for availability checks, which prevents mutually exclusive SLO and data-source selector modes.
• Pinned nobl9-go to v0.135.0-rc1.0.20260813210234-1ab7747b42f5 and updated the Go requirement to 1.26.6.

Related changes

• nobl9-go #756

Testing

• Added CLI-level Bats coverage for project-scoped SLO responses that omit metadata.project and source-SLO mappings across projects.
• Added list coverage for RFC3339 createdAt values and coarse Replay status values.
• Added request-shape coverage for SLO-only availability, Replay creation, cancellation, targeted deletion, and deletion of all queued Replays.
• Exercised the verified binary in a development environment through creation, JSON listing, terminal-state cancellation, targeted deletion, and cleanup.

Breaking Changes

Building sloctl from source now requires Go 1.26.6 instead of Go 1.26.5.