Switch to pyproject.toml, other tooling updates

[Copilot]

I took the bot changes, made them actually work, and also

• Switched to setuptools_scm, which has the benefits of
  • Not being vendored code that easily falls out of date
  • Does not require the full git history
  • Works for me locally
• Added pyproject-fmt linter
• Updated the docstring of get_forcefield_dirs_paths

Bot text below the line

Consolidates all Python packaging and tooling config into pyproject.toml, removing setup.py, setup.cfg, and MANIFEST.in.

Description

• [build-system] — setuptools + versioneer[toml]
• [project] — metadata (name, description, authors, license, readme, entry points, package data) migrated from setup.py
• [tool.versioneer] — moved from [versioneer] in setup.cfg
• [tool.coverage.run] — moved from [coverage:run] in setup.cfg
• Deleted: setup.py, setup.cfg, MANIFEST.in

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (edd7724) to head (32ad142).

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[j-wags]

The mentions of versioneer here are wrong, I think, since it was fully removed:

Description
[build-system] — setuptools + versioneer[toml]
[project] — metadata (name, description, authors, license, readme, entry points, package data) migrated from setup.py
[tool.versioneer] — moved from [versioneer] in setup.cfg
[tool.coverage.run] — moved from [coverage:run] in setup.cfg

Other than that this looks good - I installed and tested locally and was able to list installed FFs and get the package version. Thanks @mattwthompson!

[mattwthompson]

Yep that comment is out of date from changes I made after Copilot worked

I poked through logs for warnings and didn't see anything. Will merge when green. Thanks!