Fix lockfile generation to match runtime configuration

Signed-off-by: Pablo Garay <pagaray@nvidia.com>

Author: pablo-garay

.github/workflows/generate-lockfile.yml

@@ -64,23 +64,17 @@ jobs:
               curl -LsSf https://astral.sh/uv/0.8.22/install.sh | sh
               export PATH="$HOME/.local/bin:$PATH"
               
-              # Create venv with system packages
+              # Create venv with system packages (this makes container torch available)
               uv venv /opt/venv --system-site-packages
               export UV_PROJECT_ENVIRONMENT=/opt/venv
               
-              # Install minimal build deps
-              uv pip install --system setuptools wheel packaging ninja pybind11 Cython "numpy<2.0.0"
+              # Install build deps first (matches Dockerfile two-step approach)
+              uv sync --only-group build
               
-              # Backup and modify pyproject.toml
-              cp pyproject.toml pyproject.toml.backup
-              sed -i "/^override-dependencies = \[/,/^\]/s/^/# /" pyproject.toml
-              
-              # Generate lockfile
+              # Generate lockfile with the EXACT configuration from pyproject.toml
+              # No modifications! This ensures lockfile matches what Dockerfile will use
               uv lock --no-build-isolation
               
-              # Restore original
-              mv pyproject.toml.backup pyproject.toml
-              
               # Show disk usage
               df -h
             '