Migrate from scikit-build to scikit-build-core

[mtreinish]

What is the expected behavior?

The next generation of scikit-build is scikit-build-core: https://github.com/scikit-build/scikit-build-core and it looks like it'd be much easier to maintain for managing our builds of python packages. We should investigate moving qiskit-aer over to use scikit-build-core instead of scikit-build.

There is a migration guide in the documentation here: https://scikit-build-core.readthedocs.io/en/latest/migration_guide.html

CC @wshanks

[doichanj]

I have started migrating, but I found difficulty, Aer uses environment variable to define package name for qiskit-aer or qiskit-aer-gpu in setup.py

qiskit-aer/setup.py

Line 12 in 5e40517

PACKAGE_NAME = os.getenv("QISKIT_AER_PACKAGE_NAME", "qiskit-aer")

I have no idea how to define multiple package name in pyproject.toml, because tool.setuptools.dynamic does not allow name

[wshanks]

Hmm, you mention tool.setuptools.dynamic but the topic is about migrating to scikit-build-core. Can you use the regex plugin? I have not tested if it works or not for making a dynamic name:

https://scikit-build-core.readthedocs.io/en/latest/configuration.html#dynamic-metadata