ci: use commit hash for setup python action

[ReenigneArcher]

Description

Use commit hash for setup python action, so that dependabot can (hopefully) pick up the changes.

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

❗ No coverage uploaded for pull request base (nightly@328c938). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             nightly     #193   +/-   ##
==========================================
  Coverage           ?   27.75%           
==========================================
  Files              ?       10           
  Lines              ?      735           
  Branches           ?        0           
==========================================
  Hits               ?      204           
  Misses             ?      531           
  Partials           ?        0           

Flag	Coverage Δ
macOS	27.75% <0.00%> (?)

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