ci: use prerelease logic

[ReenigneArcher]

Description

• Use new prerelease logic.
• Bump plexhints action.
• Use --no-build-isolation to install pyyaml.
• Bump upload-artifact and download-artifact to v4.

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 ✅

Project coverage is 71.48%. Comparing base (a258da8) to head (8876a01).
Report is 32 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #431   +/-   ##
=======================================
  Coverage   71.48%   71.48%           
=======================================
  Files          12       12           
  Lines        1087     1087           
=======================================
  Hits          777      777           
  Misses        310      310           

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

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