Fixes the reauthentication loop of entries created with the auth add-on, and signing in again with an account that is already configured.
Fixed
- Entries created with the auth add-on asked to sign in again within minutes (#49). Their reauthentication only renewed the mobile token: it never offered "Stay signed in?" and never renewed the add-on's own web session, so the next poll found it expired again. Reauthenticating (or reconfiguring) such an entry now runs the full native sign-in and moves it to native mode for good: the add-on URL and API key are cleared and the add-on is no longer needed. An add-on that is merely installed no longer forces legacy mode for new entries either; only an add-on URL typed in during setup does.
- "already_in_progress" after a successful sign-in (#50). Adding the integration with a Microsoft account that already had an entry, usually one waiting for reauthentication, ended on that error and nothing was saved. The sign-in now updates the existing entry, closes the stale reauthentication prompt and reloads it.
- The expiry notification of legacy entries now points to the Home Assistant reauthentication instead of the add-on.