chore: cache uv .venv in cicd

.gitea/workflows/add-new-service.yml

@@ -31,22 +31,24 @@ jobs:
           SERVICE_NAME="${BRANCH#feature/add-service-}"
           echo "service_name_lower=$SERVICE_NAME" >> $GITHUB_OUTPUT
 
-      - name: Cache Python Virtual Environment
-        uses: actions/cache@v4
-        with:
-          path: .venv
-          # Changes uv.lock will automatically invalidate the cache and rebuild
-          key: ${{ runner.os }}-uv-cli-venv-${{ hashFiles('cli/uv.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-uv-cli-venv-
+      # TODO: look into venv caching (will do later in case we move from uv to pixi)
+      # - name: Cache Python Virtual Environment
+      #   uses: actions/cache@v4
+      #   with:
+      #     path: .venv
+      #     # Changes uv.lock will automatically invalidate the cache and rebuild
+      #     key: ${{ runner.os }}-uv-cli-venv-${{ hashFiles('cli/uv.lock') }}
+      #     restore-keys: |
+      #       ${{ runner.os }}-uv-cli-venv-
 
+        # # Only create the venv if the cache didn't restore an existing one
+        # if [ ! -d ".venv" ]; then
+        #   echo "Building new .venv"
+        #   uv venv .venv
+        # fi
       - name: Initialize Virtual Environment from cli/uv.lock
         run: |
-          # Only create the venv if the cache didn't restore an existing one
-          if [ ! -d ".venv" ]; then
-            echo "Building new .venv"
-            uv venv .venv
-          fi
+          uv venv .venv
           uv sync --directory cli
 
       - name: Install Ansible Galaxy Collections