pobb.in account sync

Check for duplicates

• I've checked for duplicate issues by using the search function of the issue tracker

Is your feature request related to a problem?

I'd like to be able to log in to pobb.in to keep my builds there while I get the chance to view and update them on PoB.

Describe the solution you'd like

1. Have a "Log in with pobb.in" on the build list screen. This opens some sort of web log in. I don't know if pobb.in has a mechanism to provide the token in a callback so I'm not sure how exactly it could work, so little bit of wishful thinking here.
2. This imports my pobb.in builds into the build list, maybe in a separate section, organized by patch using folders or some similar separator. These builds are re-downloaded when rendering the list anew in case they have any changes.
3. When saving a build while having a valid pobb.in token available, the build edit date is compared with the upstream in pobb.in and:

• if it's ahead, it overwrites it.
• If it's divergent, there's a dialog to choose to either overwrite it or download the latest version since conflict resolution on the encoded build string is not feasible.

4. For builds from pobb.in, there would also need to be a button somewhere in the build view, likely nearby Save, to pull the last version of the build, with a warning in case we locally have changes made after the last edit date of the pobb.in version.

Describe alternatives you've considered

A build can be imported from pobb.in by using the import functionality from PoB.
The build in PoB can be manually updated by re-pasting the new code.
The build in pobb.in can be updated by exporting it to a code in PoB, then copying it, and editing the pobb.in build by pasting it.

Additional context

No response

El issue no menciona archivos, pruebas ni puntos de entrada. Empieza localizando las implementaciones de la lista de builds y de la vista de builds, y después inspecciona el manejo existente de importación/exportación de pobb.in y cualquier límite de autenticación o de red; se consideraría terminado cuando haya un flujo de login acordado, secciones de build sincronizadas, un comportamiento ante conflictos y controles de actualización.