Windows executable

[eirikb]

Hoping to get the opinion on an implementation specific thing (looking at you @koppor 😄).

On Linux and Mac gg works roughly like this (first time, to install itself):

1. gg.cmd executed in a shell
2. executes another script
3. executes a tiny binary for download
4. executes the rust binary

But on Windows it is like this:

1. gg.cmd executed in a shell (CMD/PS)
2. executes another script for download
3. executes the rust binary

Originally Windows did the same as Linux/Mac, but I changed it to PowerShell script since I had some issues with the binary. I'm not a Windows user, so all dev happened in a VM outside my comfort zone.

The question is:
Should I convert back to using the binary for Windows?

Why I think it could be good:

1. Same setup across all OSes
2. Less jumping from this-to-that (e.g., running from say git bash in Windows will go out to PS - I think it might even fail now).
3. No need for PS at all.

One problem with the binary is that I might have to sign it - buy a cert, in order to have it not be blocked by Windows.
I didn't have this issue before, but perhaps others might.

[koppor]

Currently, gg.cmd works great on Windows without any certificate issues and it looks nice on windows:

I would not change that - and also involves less binaries ^^

---

Side track: OK, if I delete .cache while some gradle thing is running, the next stage fails, but this is not a fault of gg.cmd IMHO

c:\git-repositories\jabref>gg.cmd gradle tasks

thread 'main' panicked at src\main.rs:270:18:
called `Result::unwrap()` on an `Err` value: "Binary not found"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[eirikb]

Related to #146 (except 146 is more general) - closing this since keeping the PS is the way forward.