v2.0.3 — fix cloud setup WAF 403

What's Changed

Bug Fixes

• Cloud setup no longer fails with a misleading "invalid email or password" error. Orbit's API gateway (WAF) had begun returning HTTP 403 to any request whose User-Agent contains HomeAssistant — which is exactly what Home Assistant's shared aiohttp session stamps on outbound requests by default — so every cloud call at setup was rejected before authentication and config_flow mislabeled the 403 as bad credentials. The integration now sends a browser User-Agent (and a normal Accept) on its cloud REST calls, matching the wider B-Hyve HA ecosystem's fix for the same WAF change (sebr/bhyve-home-assistant#427). This integration is BLE-based and only contacts the cloud at setup, so the change is confined to the setup path. Fixes #1. Thanks @exactmike!

Maintenance

• Bump manifest.json version to match the release tag.

Full Changelog: v2.0.2...v2.0.3