ci: fix code coverage

[ReenigneArcher]

Description

Fix coverage reports after #17 inadvertently re-ordered some things related to coverage.

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

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (master@8fa9d69). Click here to learn what that means.

Additional details and impacted files

@@            Coverage Diff            @@
##             master      #25   +/-   ##
=========================================
  Coverage          ?   44.75%           
=========================================
  Files             ?        7           
  Lines             ?      324           
  Branches          ?      177           
=========================================
  Hits              ?      145           
  Misses            ?       42           
  Partials          ?      137           

Flag	Coverage Δ
Linux	63.82% <ø> (?)
Windows	44.29% <ø> (?)
macOS	51.66% <ø> (?)

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