[ci] use uv to manage Python and pip dependencies

The GitHub-provided setup-python action does not create portable
binaries and can cause failure for bitstream cache. Instead, ask
uv to manage our dependencies.

Signed-off-by: Gary Guo <gary.guo@lowrisc.org>

Author: nbdd0121

.github/actions/install-deps/action.yml

@@ -22,6 +22,10 @@ inputs:
     description: Path at which to install Verible
     required: true
     default: /tools/verible
+  venv-path:
+    description: Path at which to place Python venv
+    required: true
+    default: ~/.local/share/venv
 
 runs:
   using: composite
@@ -32,15 +36,29 @@ runs:
         grep '^[^#]' apt-requirements.txt | xargs sudo apt install -y
       shell: bash
 
-    - uses: actions/setup-python@v5
+    - uses: astral-sh/setup-uv@v3
       with:
-        python-version: '3.8'
-        cache-dependency-path: python-requirements.txt
-        cache: pip
+        version: '0.4.20'
+        enable-cache: true
+        cache-dependency-glob: |
+          pyproject.toml
+          python-requirements.txt
+
+    - name: Install Python
+      shell: bash
+      run: |
+        uv python install 3.8
+        # Create a virtual environment for UV
+        uv venv ${{ inputs.venv-path }}
+        echo "${{ inputs.venv-path }}/bin" >> "$GITHUB_PATH"
+        echo "VIRTUAL_ENV=${{ inputs.venv-path }}" >> "$GITHUB_ENV"
 
     - name: Install Python dependencies
-      run: python3 -m pip install -r python-requirements.txt --require-hashes
       shell: bash
+      run: |
+        uv pip install -r python-requirements.txt --require-hashes
+        # We installed uv from setup-uv action, so uninstall from venv to prevent conflict
+        uv pip uninstall uv
 
     - name: Install Verilator
       run: |