BioNodulo Desktop desktop-v0.1.0-alpha.10

Release 0.1.0-alpha.10 — rebuild a Python environment that cannot start

The reported Windows failure was a venv left behind by an earlier install:

    Backend exited (exit code: 103) before becoming ready.
    No Python at '"C:\...\python-embedded\python.exe'

On Windows the venv's python.exe is a launcher stub that resolves its real
interpreter from `home` in pyvenv.cfg. The venv lives in the user's data
directory, which an upgrade does not touch, while the bundled interpreter it
points at belongs to the installation being replaced. The stub is then aimed at
a path its own app no longer owns, and every launch exits 103 -- unrecoverable
without deleting a folder the user has no reason to know about.

Existing is no longer taken as working: the interpreter is asked for its
version, and a venv that cannot answer is rebuilt, both during setup and at
startup. A Windows CI job now provisions the way the app does -- with the
bundled interpreter rather than letting uv fetch one, which an installed app
cannot do -- and fails on a quoted or dangling `home` before proving the venv's
python launches. That job passes, which is what confirms the shipped bundle is
sound and the fault was the stale environment.

Python was already bundled; that part needed no change.

Also carries the exit and relaunch fixes: the app now actually exits, and a
second launch surfaces the running window instead of being swallowed.