Update packaging for current standard practice using pyproject.toml

[dcslagel]

Describe the request
The trend in Python packaging is to move away from setup.py toward pyproject.toml.
So Lasio's packaging should keep reasonably up-to-date on packaging practices and start to migrate toward pyproject.tom.

Expected behavior
Continue to package Laiso into an equivalent package as the one currently made with setup.py.

Software versions (please complete the following information):

• Python version: [3.10]
• Python distribution: Homebrew
• lasio version (0.30)

Additional context
Current build cmd:
python setup.py bdist_wheel --universal
displays this warning:
.../python3.10/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer....

[dcslagel]

02-07-2023 Updates:
I experimented with moving as much as possible from setup.py to pyproject.toml on branch:
https://github.com/dcslagel/lasio/tree/explore_newer_packaging_techniques_02

Findings:

• I had to remove the test for Python 3.6 because it doesn't integrate with the newer versions of setuptools that support pyproject.toml. Given that and that Python 3.5 and 3.6 are considered end-of-life, I created issue End Lasio support for Python 3.5 and 3.6 ? #549 to discuss removing Lasio support for them.
• Because of the current dynamic way that Lasio identifies the version, the setuptools_scm configuration had to stay in setup.py for now in-order to successfully build and test in the GitHub workflow.

setup(
     use_scm_version=True,
     setup_requires=["setuptools_scm"]
)

There is probably a way to get it moved on over to pyproject.toml, so that can be a future iteration..

[kinverarity1]

Thanks for bringing this up. I'm happy to move to whatever the recommended solution is - packaging has always been changing and hard to get right.