bug(backend): if there is a qri connect process already running, ensure it is up-to-date

[ramfox]

We've had a few users come to us with issues when they have been using an older version of Qri & are now downloading and launching the new Qri Desktop.

We recently refactored the start-up process in Desktop, that more robustly checks that the version of Qri core you have in your PATH is compatible with the version of Desktop you are running before we launch the backend daemon. However, we also allow Desktop to piggyback off of already running processes. This allows an advanced user to run Qri core on their own via the CLI, especially if they are trying to use a Qri repo that is not saved in the default location.

But, we are not checking to see if that already running Qri process is compatible with the version of Desktop the user is running! To remedy this, if there is a qri connect process running, and it's out of date, kill the process and launch our own.

We can tell if a process is out of date by fetching from the /version endpoint and comparing the result with the expected backend version.