workflows: Fix uv call

[jku]

No description provided.

[woodruffw]

Oops, didn't mean to self-improve that suggestion.

(I switch it to uv tool install since uv pip install will fail in this case, without a venv. uv tool install is the right way to install an isolated tool.)

[jku]

Oh I see: I guess then we can also use uvx directly to avoid the install step

I think we managed to get to a state where neither one can approve... I'll force-push a fix

[jku]

uv tool install is the right way to install an isolated tool

I am not sure I actually agree with this for CI: there is no way to use pinned versions with uv tool AFAICT. Longer term I think we should aim to have all our build/dev tools listed in uv.lock, and should use those versions -- at least then we'd get a benefit from the busy work of maintaining a lock file

[jku]

actually uvx pip-compile does not work because that's not the package name. Will fix