Switch publish workflow to use standard Python setup

Using actions/setup-python instead of uv for PyPI publishing
to avoid externally managed Python issues

Author: bdmorin

.github/workflows/publish.yml

@@ -11,23 +11,24 @@ jobs:
     steps:
     - uses: actions/checkout@v4
 
-    - name: Install uv
-      uses: astral-sh/setup-uv@v4
-    
     - name: Set up Python
-      run: uv python install 3.11
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.11'
+    
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build twine
     
     - name: Build package
-      run: uv build
+      run: python -m build
 
     - name: Check package
-      run: |
-        uv pip install --system twine
-        twine check dist/*
+      run: twine check dist/*
 
     - name: Publish to PyPI
       env:
         TWINE_USERNAME: __token__
         TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
-      run: |
-        twine upload dist/*
+      run: twine upload dist/*