Tidy GitHub workflows

[alexdewar]

As with many of our projects, FINESSE currently has one large workflow file which does several different things (running tests, building documentation, building release artifacts) and I thought it would be cleaner to try to separate this out a bit.

Specifically:

• I made separate composite actions for installing dependencies, building the docs and building the EXE file
• I made two new workflows for deploying the documentation and uploading the release artifacts (viz. generated EXE file)

The docs workflow uses the new GitHub Actions method for deploying docs rather than the gh-pages branch, which brings a few advantages. I tested that the action actually works by deploying from this branch.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.80%. Comparing base (6d86e1b) to head (577d0b8).
Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #655      +/-   ##
==========================================
+ Coverage   84.67%   84.80%   +0.12%     
==========================================
  Files          69       69              
  Lines        3452     3448       -4     
==========================================
+ Hits         2923     2924       +1     
+ Misses        529      524       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dalonsoa]

This is pretty cool! I didn't know about "composite" and I bet others don't know, either. I suggest you report this in Teams or in the next team meeting.

[alexdewar]

This is pretty cool! I didn't know about "composite" and I bet others don't know, either. I suggest you report this in Teams or in the next team meeting.

Neither did I but it seems handy! I'll bring it up in the team meeting.