Move to `hatch` as a python project tool

[devraj]

I've been tracking if poetry is suitable for our projects (specially as it comes to managing libraries) - don't get me wrong poetry does wonders.

This is based on the analysis of what some of our major library vendors are using, and where the ecosystem is going in terms of a PEP665 compliant tool.

I have decided to move our projects to hatch and this is a ticket to move this project (first amongst anomaly projects) to hatch.

Note that we should produce substantial documentation on how we moved from poetry to hatch.

See also:

• django-hatch-startproject
• Anna-Lena Popkes: An unbiased evaluation of environment management and packaging tools by @zotroneneis

[devraj]

Seeing that hatch can run commands and manage the environments, we might not actually need our Taskfile anymore.

I will investigate this further, document it and then make a decision based on what I am able to automate.

[devraj]

Notes to follow up on post migration:

• Github action will need to change to use hatch to manage dependencies and run the tests
• Documentation needs to be updated to reflect how we use hatch in the project
• Notes around how dependencies are managed when using hatch

[devraj]

Leaving a note her that hatch does not support lock files at the moment and package dependency management is still done by editing pyproject.tom (or from what I can see anyway).

Studying the venn diagram and watching @zotroneneis's presentation, peotry may still be our most viable option for now (apart from it missing managing version numbers)

[devraj]

See comment on anomaly/lab-python-server by @juftin highlighting pip-compile