fix: remove incorrect RefreshToken throw from Bluesky provider

[smith-and-web]

Summary

• Removes the RefreshToken exception throw from getAgent() in the Bluesky provider
• Bluesky uses password-based auth (stored in customInstanceDetails), not OAuth tokens
• The refreshToken() method returns empty values, so throwing RefreshToken caused integrations to disconnect

Problem

When the Bluesky getAgent() method encountered a login error, it threw RefreshToken. This triggered the token refresh flow in RefreshIntegrationService, which:

1. Called refreshToken() on the Bluesky provider
2. Got empty/invalid values back (since Bluesky doesn't implement token refresh)
3. Called disconnectChannel() since refresh "failed"

This caused Bluesky integrations to be marked as disconnected even for transient errors.

Solution

Let login errors propagate naturally instead of wrapping them in RefreshToken. This allows upstream code to handle the error appropriately without triggering the token refresh flow that doesn't apply to password-based providers.

Test plan

• Connect a Bluesky account and verify posting works
• Temporarily use invalid credentials and verify the error is handled gracefully (not triggering token refresh)
• Verify the integration doesn't get disconnected on transient network errors

[vercel]

@smith-and-web is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.