v0.1.75 - Update Platform API contract (#96)

🌟 Summary

Release v0.1.75 brings video-frame skipping to cloud prediction, improves validation and saved video outputs, and synchronizes the Platform API contract with its Python SDK.

📊 Key Changes

• 🎞️ Cloud video prediction supports vid_stride: The option is sent to Platform, which predicts every Nth frame. Local output saving now uses the same frame selection, keeping predictions, labels, crops, and video frame rate aligned.
• 🛡️ Invalid prediction settings are rejected early: ul cloud predict checks arguments before uploading a local model or sending a Platform request. For example, vid_stride=0 fails before a prediction can incur a charge.
• 🔗 API and SDK updated to version 0.1.75: The OpenAPI contract and generated Python SDK now include optional vid_stride for model and deployment prediction requests; its minimum value is 1.
• 🧪 Expanded validation and clearer errors: CI now tests saved cloud-prediction outputs offline with CPU-based dependencies. CLI messages for authentication and connection failures are clearer, and SDK connection errors provide a fallback message when the underlying error is blank.

🎯 Purpose & Impact

• ✅ Makes cloud video predictions behave more consistently with local YOLO prediction, especially when saving results.
• 💸 Prevents invalid prediction arguments from triggering an unnecessary Platform request.
• 📦 Keeps the API contract, generated SDK, and package version in sync, so developers can rely on the SDK reflecting the supported API behavior.

What's Changed

• Honor vid_stride in ul cloud predict, test prediction saving, and clarify CLI errors by @glenn-jocher in #93
• Validate ul cloud predict arguments before the Platform request by @glenn-jocher in #94
• Send vid_stride to Platform predict and share the CLI test loopback server by @glenn-jocher in #95
• Update Platform API contract by @UltralyticsAssistant in #96

Full Changelog: v0.1.74...v0.1.75