fix: improve default error handling #1379 #1409

[Alexj9837]

Fixes #1379
Fixes #1409

Both issues related to error handling in the REST client.

1379 - Catches 'UnauthorisedAccessErrorexplicitly instead of string-matching onBlueskyRemoteControlError`.

1409 - Expands the exception hierarchy so each
HTTP status code raises a distinct typed exception rather than bundling
everything into BlueskyRemoteControlError.

Tests

• Update tests to match new exception signatures
• Add missing coverage for 422 non-list detail response
• Add missing coverage for streaming error in run command

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.28%. Comparing base (e7eae6c) to head (04973f0).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1439      +/-   ##
==========================================
+ Coverage   95.19%   95.28%   +0.08%     
==========================================
  Files          43       43              
  Lines        3119     3136      +17     
==========================================
+ Hits         2969     2988      +19     
+ Misses        150      148       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ZohebShaikh]

Looks good only few things can be tidied up

[tpoliaw]

What are these asserts testing for?

[Alexj9837]

It was a leftover from when BlueskyRemoteControlError had a fixed response that broke with the new error messsages. It only checks the body is non-empty. I can remove this or I could add a description to the 400 responses in set_state, like "Cannot transition from {current_state} to {new_state}") and check that instead? might be better for debugging