Make release workflow reusable

[ehennestad]

• More robust way of getting the MLTBX path in the workflows, i.e by having it returned from the packageToolbox function
• Hardcode compatible python versions in the workflow, and build the matrix.include dynamically?
• Determine MATLAB releases to test based on min and max release from MLToolboxInfo

[github-actions]

Test Results

21 tests   21 ✅  18s ⏱️
 5 suites   0 💤
 1 files     0 ❌

Results for commit b9e7294.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.05%. Comparing base (b323a59) to head (b9e7294).
Report is 30 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   41.11%   43.05%   +1.93%     
==========================================
  Files          53       56       +3     
  Lines        1182     1361     +179     
==========================================
+ Hits          486      586     +100     
- Misses        696      775      +79     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.