ci: create release on push events

[ReenigneArcher]

Description

Create a release and upload test binaries as artifacts.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.85%. Comparing base (505c90b) to head (47a2350).
Report is 24 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   93.85%   93.85%           
=======================================
  Files          34       34           
  Lines        1839     1839           
  Branches     1023     1023           
=======================================
  Hits         1726     1726           
- Misses         49       51    +2     
+ Partials       64       62    -2     

Flag	Coverage Δ
Linux	89.37% <ø> (ø)
Windows	93.79% <ø> (ø)
macOS	69.38% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

[FrogTheFrog]