Modernise setup

[ZedThree]

• Move to using setup.cfg over setup.py
  • This is the preferred way recently, as it enables working with more build tools
• Add install dependencies
  • All the dependencies now get pulled in during installation
• Get the version from git using setuptools_scm
  • This enables the reported version to include e.g. the commit hash if not using a released version. It also means bumping the version is as simple as creating a new release on Github

[shimwell]

Hi Chris all these updates look great, wondering what you thought are on use a /src/inference folder instead of a /inference folder

[C-bowman]

Hi Jon!

I hadn't heard of putting the package in an /src/ folder, but it does seem that's how the PyPA have it in their example package.

These updates are thanks to Peter who is making improvements as part of his PlasmaFAIR project - I'll get his thoughts on it when we speak next.

[ZedThree]

I don't usually use a src/ directory for python projects, unless they're particularly complex, for example due to having multiple top-level modules. For something like inference-tools, I don't think there's any benefit (although also no significant cost either!)

[shimwell]

Nice, python publish action, I didn't know about that one. I currently do something similar but without using the pypa/gh-action-pypi-publish@release/v1. I'm learning lots for these PRs , thanks for teaching good practice.