Fix CI for publishing

[chris-zen]

This PR provides the following novelties:

• Using pyproject.toml
• Support for uv
• Supporting cython in the build
• A Makefile with common development tasks (checking code, building packages and docker, publishing packages and docker, ...)
• Producing and publishing packages for all the supported python versions (3.8, 3.9, 3.10, 3.11) and platforms (linux, macos)

[FedericaBrando]

Looks great, I just spot a typo in the make that I've commented. :)

thanks a lot! 😄

[FedericaBrando]

I was checking the README.md and this part is not contained in the Makefile:

oncodrivefml/README.md

Lines 84 to 90 in 628fece

	```bash
	git clone [email protected]:bbglab/oncodrivefml.git
	cd oncodrivefml
	make install-dev
	source .venv/bin/activate
	oncodrivefml --help
	```

while in the Makefile the install-dev is not present. How would the readme change in this case?

[chris-zen]

I was checking the README.md and this part is not contained in the Makefile:

oncodrivefml/README.md

Lines 84 to 90 in 628fece

	```bash
	git clone [email protected]:bbglab/oncodrivefml.git
	cd oncodrivefml
	make install-dev
	source .venv/bin/activate
	oncodrivefml --help
	```

while in the Makefile the install-dev is not present. How would the readme change in this case?

Fixed. Added build-dev to the Makefile and updated the README.md