ci: use new LizardByte setup python action

[ReenigneArcher]

Description

This PR moves to the new LizardByte setup python action.

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 #174 (516916c) into nightly (964b3b9) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff            @@
##           nightly     #174   +/-   ##
========================================
  Coverage    68.97%   68.97%           
========================================
  Files           10       10           
  Lines          735      735           
========================================
  Hits           507      507           
  Misses         228      228           

Flag	Coverage Δ
Linux	68.97% <ø> (ø)
Windows	68.97% <ø> (ø)
macOS	68.97% <ø> (?)

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