Ngio projection task

[lorenzocerrone]

• refactor task core to use ngio > 0.2
• update current testing
• add additional testing tailored to flexibility

Checklist before merging

• I added an appropriate entry to CHANGELOG.md

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
fractal_tasks_core/tasks
copy_ome_zarr_hcs_plate.py					48-49, 193
projection.py					46
Project Total

This report was generated by python-coverage-comment-action

[jluethi]

This looks very promising, great to see how much ngio simplifies things. I added a few minor comments to the task code, will review the tests later :)

[jluethi]

I added a few very minor comments. Besides that, all looks great and I'd say this PR is ready to be merged into dev-1.5!

[lorenzocerrone]

@tcompa I have started refactoring the task tests (see the tests/task_v2). It would be great if you could go over it and look if it all looks alright for you.

[tcompa]

I have started refactoring the task tests (see the tests/task_v2). It would be great if you could go over it and look if it all looks alright for you.

Quick generic question: will you include both old (non-tests/tasks_v2) and new tests, or only the new ones (e.g. for the projection task)? In both cases, I guess we should we enable them from the GitHub action? (they are currently skipped)
And then, in case you want to stick to the new tests only, I suggest to remove the old ones - so that you'll get an overview of whether you are missing out a lot of coverage or not.

[lorenzocerrone]

I have started refactoring the task tests (see the tests/task_v2). It would be great if you could go over it and look if it all looks alright for you.

Quick generic question: will you include both old (non-tests/tasks_v2) and new tests, or only the new ones (e.g. for the projection task)? In both cases, I guess we should we enable them from the GitHub action? (they are currently skipped) And then, in case you want to stick to the new tests only, I suggest to remove the old ones - so that you'll get an overview of whether you are missing out a lot of coverage or not.

My idea would be to keep both of them for now (at least during the refactoring of the first few tasks). We remove the ' task ' tests only when we are confident that the new task_v2 testing offers comparable coverage.

Yes, we need to enable them! Sorry, I overlooked that

[tcompa]

@tcompa I have started refactoring the task tests (see the tests/task_v2). It would be great if you could go over it and look if it all looks alright for you.

I added some minor comments, but it definitely looks fine to me.
Let me know if there are specific questions or parts to review in detail.