Log out the temporary 3party device when the upgrade fails

[CDRussell]

Task/Issue URL: https://app.asana.com/1/137249556945/project/608920331025315/task/1218692308523756?focus=true
Tech Design URL (if applicable):
API Proposals URL(s) (if applicable):

Description

Pairing Android with a 3party code fails correctly when that account already has a native DDG device, but it can leave Android showing as a synced device incorrectly. That's one example of a failure path and there are a few others
like it.

This PR makes it so that when we hit an error, we do a best-effort logout of the device Android registered during the 3party login, which is what the Windows and Apple clients do already.

Steps to test this PR

Need two devices/emulators to test fully.

• Fresh install from this branch on two Androids internal variant
• Set up sync on Device A (meaning this account will have a ddg credential)
• On Device A still, go to sync dev settings
• Tap Create 3party Credential button, then Copy 3party Recovery Code button
• On Device B, set up sync Sync With Another Device, and paste the 3party recovery code
• Verify Device B shows "already upgraded" error
• On Device A, allow the device list to refresh and verify that Device B is not there

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[cmonfortep]

LGTM