feat(workflows): Use python3 for venv and version check

Updated the GitHub Actions workflow in `.forgejo/workflows/release.yml` to explicitly use `python3` instead of `python` for both version checking and virtual environment setup. This change ensures compatibility and clarity across environments where `python` might still point to Python 2.x, preventing potential conflicts and erasing ambiguity. The adjustment aligns with modern best practices, acknowledging the widespread transition to Python 3 and its tooling.

.forgejo/workflows/release.yml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
   push:
     tags:
-      - '*'
+      - "*"
 
 jobs:
   setup:
@@ -23,8 +23,8 @@ jobs:
 
       - name: Set up Python environment
         run: |
-          python -V
-          python -m venv venv
+          python3 -V
+          python3 -m venv venv
           source venv/bin/activate
           pip install -U pip
           pip install .[all]
@@ -45,7 +45,7 @@ jobs:
 
       - name: Set up Python environment
         run: |
-          python -m venv venv
+          python3 -m venv venv
           source venv/bin/activate
 
       - name: Install publishing tools
@@ -60,4 +60,4 @@ jobs:
         run: |
           python -m twine upload --username __token__ --password ${PYPI_TOKEN} dist/*
         env:
-          PYPI_TOKEN: ${{ secrets.PYPI_TOKEN }}
+          PYPI_TOKEN: ${{ secrets.PYPI_TOKEN }}