Move to setuptools from poetry build no longer installs binary entrypoint

This change: https://github.com/DataDog/guarddog/commit/eb1910260168e3c414ce0a71be236f192645a0ab

More specifically this change: https://github.com/DataDog/guarddog/blob/e918bfd4e7497f9b54be1779381eb0dc52391084/pyproject.toml#L64-L66

Causes ~/.local/bin/guarddog to not be “installed” as a script entry point using pip. You can still run guarddog with python -m guarddog scan archinstall but it will fail for github runners using the pip install git+https://github.com/DataDog/guarddog.git method: https://github.com/Torxed/archoffline/actions/runs/3576043149/jobs/6013361779#step:9:5

I’m not sure what setuptools expect during pip install to get this working sadly, more used to poetry and flit. It doesn’t seem that this is helping, but it’s what I would expect to work:

[project.scripts]
guarddog = "guarddog.cli:cli"

But it’s doubtful that this will ever work with the current build system:

[tool.poetry.scripts]
guarddog = "guarddog.cli:cli"

Saving possible related pep saying this should be possible: https://peps.python.org/pep-0660/

[christophetd]

Something went terribly wrong here, looking into it

[Torxed]

Will do, thank you for the quick turnaround 😃 Keep it up!