We currently add in the project before running uv sync as opposed to adding just the uv.lock/pyproject.toml and syncing the environment first.

This makes poor use of the build cache, but needed to be done since doing a uv pip install --no-deps -e . after the uv syncs to warm the cache, still caused a uv sync at runtime. This suggests something about uv pip is not congruent with the uv sync and we should explore other ways to be more efficient with the build cache.

One option is just to naively copy after the final uv sync since the project is installed editable, but we need to think about that carefully since it may not be correct to copy all things into the container without a reinstall, e.g., the egg info/editable metadata