move build configuration into pyproject.toml

[zacharyburnett]

Description

setuptools now supports the [project] table, which is defined by PEP621.

Additionally, setuptools now supports its own entry in pyproject.toml called [tool.setuptools] (pypa/setuptools#1688, https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html#setuptools-specific-configuration); however, it comes with the following disclaimer:

Support for declaring configurations not standardized by PEP 621 (i.e. the [tool.setuptools] table), is still in beta stage and might change in future releases.

Reading toml is supported natively in Python 3.11 with tomllib

Given this, we can attempt to consolidate the build configuration into a single pyproject.toml file that can possibly be read by other build systems in the future.

Change log entry

• Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
  list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
  should add a no-changelog-entry-needed label.

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

• Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
• Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
• Do the proposed changes follow the STScI Style Guides?
• Are tests added/updated as required? If so, do they follow the STScI Style Guides?
• Are docs added/updated as required? If so, do they follow the STScI Style Guides?
• Did the CI pass? If not, are the failures related?
• Is a milestone set?
• After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

[pllim]

It is a little too early for this. You will need a very new version of pip.

We should wait for several more releases from Python org.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (4b72cd3) 91.75% compared to head (708139b) 91.75%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1661   +/-   ##
=======================================
  Coverage   91.75%   91.75%           
=======================================
  Files         147      147           
  Lines       16186    16186           
=======================================
  Hits        14852    14852           
  Misses       1334     1334           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[rosteen]

I resolved the conflicts, let's see if the tests pass this time...I installed in a few environments locally and everything seemed to work fine.

[rosteen]

Had to kick the tests a couple times, but they finally passed. I pushed one fix to the sphinx config section, I think this is good to go now.

[duytnguyendtn]

Local install works on my end. Installation is successful, can import jdaviz and the SpecvizExample notebook works great. Thanks for the contribution!