Migrate to python poetry

[HYP3R00T]

For now, we are using the traditional way of managing python, i.e. using requirements.txt.

The problem with traditional way is that we are not controlling which python version to use. We have create virtual environment manually (using python3 -m venv any-random-name-for-the-virtual-environment) which could be a problem if someone accidently pushes their venv to the repo. If we use python poetry, will be never have to worry about it as it won't create the virtual env within the repo.

I am suggesting we should move to python-poetry. This way, we can manage everything related to python, within one single pyproject.toml file. We can separate dependencies (for instance putting mkdocs in dev dependencies). We can strictly mention which python version to use. If we plan to use python scripting in future, we can customize ruff linting and formatting within the same file.