Replace setup.py workflow

[merelcht]

Also note that setup.py is deprecated and we will have to move away from it in general

Originally posted by @datajoely in #1607 (comment)

The setup.py workflow is deprecated and we should move towards another way of packaging in Kedro. Ideally we would move to a pyproject.toml driven workflow as described here: https://packaging.python.org/en/latest/tutorials/packaging-projects/, but until that's the official way of doing things we should probably use setup.cfg file: https://setuptools.pypa.io/en/latest/userguide/declarative_config.html

[merelcht]

Check what Alloy team is doing for packaging, would be good to understand what approach they are taking and why.

[deepyaman]

Also note that setup.py is deprecated and we will have to move away from it in general

As mentioned in the second paragraph of the TL;DR, direct invocation of setup.py is deprecated, not the use of setup.py itself. It should be a relatively small change to properly specify the build system. Moving to setup.cfg-/pyproject.toml-based workflows do have their own advantages, but we can separate this until the pyproject.toml approach is out of beta and/or we know whether to move down the setup.cfg or pyproject.toml route, in order to minimize documentation (and other user-facing) changes.

[datajoely]

The argument for adopting setup.cfg is that it makes the eventual migration much simpler. So it's just a question of when you front load your development effort - One huge ticket or two smaller ones.

[merelcht]

Closing in favour of #2152