Release windows executable as part of release-deploy

[smjoshiatglobus]

• Added a new workflow to build executables on Windows when a pull request is opened
• For windows only, added steps to build and deploy windows executables to GitHub release.
• If this PR looks good, it can replace PR #108.

[codecov-commenter]

:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.93%. Comparing base (e8644e2) to head (bf12ac0). Report is 26 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #110 +/- ## ========================================== + Coverage 89.82% 89.93% +0.10% ========================================== Files 15 15 Lines 1632 1669 +37 ========================================== + Hits 1466 1501 +35 - Misses 166 168 +2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[smjoshiatglobus]

Yes, please! Keeping my fingers crossed!

[mrbean-bremen]

Nope, didn't work. I will check later...

[smjoshiatglobus]

Bummer! I do see that the executable was built correctly in the job. I double-checked and confirmed that action-gh-release specifies using / for directory separator even for Windows. I still have much to learn!

[mrbean-bremen]

I have hacked it to work (by amending the commit and re-creating the release several times). The actual problem was an error in the GH release action that I also missed: you had put an hyphen before the file names:

      with:
        files: |
          - dist/validate_iods.exe
          - dist/dump_dcm_info.exe

which should have been:

      with:
        files: |
          dist/validate_iods.exe
          dist/dump_dcm_info.exe

(e.g. these are not sub-items, but just the file names) I actually replaced it with:

      with:
        files: dist/*.exe

I also divided the workflow into two separate jobs, so that the pypi release depends on the successful executable creation, to avoid the problem for future releases. I did this by force-pushing the changes to avoid to have to make a new PyPi release, not really the clean way... but we do have a release including the executables now, so thank you for the contribution!

[smjoshiatglobus]

Ah! My bad! Thank you for fixing it. I can now point others to the release page for downloading the executables!