fix: add .venv/bin to PATH in container Dockerfile

[aidandaly24]

Description

Container builds using uv sync fail at runtime with exec: "opentelemetry-instrument": executable file not found in $PATH. This happens because uv sync ignores UV_SYSTEM_PYTHON=1 and always creates a .venv directory, installing console scripts to /app/.venv/bin/ which is not on $PATH. This adds /app/.venv/bin to PATH in the container Dockerfile template.

The other alternative solution is to switch from uv sync to uv pip install --system . which would actually install to system Python and put scripts in /usr/local/bin. This would also make UV_SYSTEM_PYTHON=1 meaningful.

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran npm run test:unit and npm run test:integ
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	44.13%	2997 / 6790
🔵	Statements	43.71%	3155 / 7217
🔵	Functions	46.07%	622 / 1350
🔵	Branches	48.49%	1935 / 3990

Generated in workflow #790 for commit 3a3b55c by the Vitest Coverage Report Action