refactor: setup.py -> pyproject.toml

[jacobjove]

Closes #659

[Stranger6667]

I'd vote against having Poetry-specific content in pyproject.toml

[Stranger6667]

Instead, I'd suggest specifying dependencies as described in the pyproject.toml spec.

[benjaoming]

Nice work @iacobfred 🙏

Agreeing with @Stranger6667, I don't see the current benefit of using Poetry. And even if switching to a tool like this, I would prefer hatch.. but then we have to do a lot of extra work to migrate current Tox-based environment management and CI. Which I think is too much for one changeset.

Would you be able to change to a version of pyproject.toml to be without Poetry and we just use [project.optional-dependencies] like @Stranger6667 linked?

[benjaoming]

@Stranger6667 if we switch to hatch, we can get rid of the setup.py-based builder alltogether. Would you be good with that?

For instance like this:

https://github.com/django-wiki/django-wiki/blob/cf980084d222775458c976703972b7edca9aa07f/pyproject.toml#L67

and

https://github.com/django-wiki/django-wiki/blob/cf980084d222775458c976703972b7edca9aa07f/pyproject.toml#L84-L85

We could also use hatch to get rid of the Makefile and MANIFEST.in.

[Stranger6667]

@benjaoming Yep!