Handle refresh token exception

[MartinHjelmare]

The callback is defined outside of this library so we need to handle exceptions when calling it.

[augmentcode]

🤖 Augment PR Summary

Summary: Makes realtime reconnects tolerate failures from user-supplied access-token refresh callbacks.

Changes:

• Wraps the top-level Tibber refresh callback invocation in exception handling.
• Logs callback failures and continues the reconnect flow without a refreshed token.
• Adds a regression test that verifies a failed callback does not prevent transport reconstruction.

Technical Notes: Successful refresh behavior, including synchronizing a changed token with the data API, remains unchanged.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

TibberRT is also an exported public class and accepts refresh_access_token directly, but its reconnect() still awaits that callback unguarded at tibber/realtime.py:154. Consequently, direct TibberRT users still have reconnect abort when their externally defined callback raises, despite the behavior this change intends to provide.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[MartinHjelmare]

I don't think TibberRT is expected to be called separately, but in any case I think that's a separate problem.