ci: use rolling releases

[ReenigneArcher]

Description

This PR will move the project to a rolling release model.

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

Merging #192 (7450f91) into master (d89367b) will not change coverage.
Report is 1 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #192   +/-   ##
=======================================
  Coverage   69.68%   69.68%           
=======================================
  Files          12       12           
  Lines         983      983           
=======================================
  Hits          685      685           
  Misses        298      298           

Flag	Coverage Δ
Linux	69.68% <ø> (ø)
Windows	69.48% <ø> (ø)
macOS	69.48% <ø> (ø)

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