Support uv

[woutdenolf]

Continue with #41. This PR adds UV and refactors tests. AI warning.

[codecov]

Codecov Report

❌ Patch coverage is 90.00000% with 12 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/ewoks/_requirements/utils/freeze_manager.py	88.23%	6 Missing ⚠️
src/ewoks/_requirements/conda.py	0.00%	1 Missing ⚠️
src/ewoks/_requirements/pipenv.py	0.00%	1 Missing ⚠️
src/ewoks/_requirements/pixi.py	0.00%	1 Missing ⚠️
src/ewoks/_requirements/poetry.py	0.00%	1 Missing ⚠️
src/ewoks/_requirements/utils/base_manager.py	75.00%	1 Missing ⚠️
src/ewoks/_requirements/uv.py	97.29%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[woutdenolf]

@loichuder Not done yet. But I'm not familiar with uv so I'm not sure using uv in this way makes sense. Perhaps I should focus on creating fresh environments and drop support for installation in the current environment?

[woutdenolf]

To be more specific, we use uv pip here (uv pip install, uv pip freeze) which is why we have a common base logic with pip in the refactored pip/uv managers and tests.

If we refactor and drop installation in the current environment then we have "pip+venv" (native), "uv", "pixi", "conda", "poetry" (we can drop "pipenv").

[loichuder]

Discussed in-person. Based on the fact that most modern package managers abstract away virtual env management, we decided that ewoks install should do the same. That means we should not have to enter manually in a venv: ewoks install should create a new env for us or use whatever machinery the underlying packing manager is using to abstract the venv.

However, to cater for dev/debugging usecases, we will add a flag --in-place to keep the current behaviour (that is, installing in the current env) for pip and uv.

[woutdenolf]

Abandoned this PR in favor of what was discussed.

Current WIP #330 to be split in parts when finished.