fix: add --project flag to uv entrypoint for GitHub Actions compatibility

[jmeridth]

Problem

The uv migration introduced a runtime regression in the Docker image. GitHub Actions' Docker container runner overrides the working directory to /github/workspace via --workdir, which causes uv run to not find the pyproject.toml at /action/workspace. It falls back to system Python (which has no packages installed), resulting in:

ModuleNotFoundError: No module named 'github3'

Fix

Add --project /action/workspace to the ENTRYPOINT so uv always discovers the project and its .venv regardless of the runtime working directory.

Testing

Verified locally with Docker:

Test	Outcome
Before fix (--workdir /github/workspace)	ModuleNotFoundError: No module named 'github3' ❌
After fix (--project /action/workspace)	Imports succeed, runs correctly ✅

[Copilot]

Pull request overview

Updates the Docker image entrypoint so the GitHub Actions container runner’s overridden working directory (/github/workspace) no longer prevents uv run from finding the project at /action/workspace, avoiding fallback to system Python and missing dependencies.

Changes:

• Add --project /action/workspace to the Docker ENTRYPOINT so uv reliably discovers pyproject.toml and the .venv regardless of runtime working directory.