Add GKX (renamed from spectraxgk)

[RKHashmani]

This adds a recipe for gkx, the renamed continuation of spectraxgk (existing feedstock: https://github.com/conda-forge/spectraxgk-feedstock). Upstream renamed the project from SPECTRAX-GK to GKX and now develops it at https://github.com/uwplasma/GKX. PyPI spectraxgk stops at 1.7.0 and PyPI gkx continues from 1.7.1, so conda-forge currently has no path forward for this package under the old name.

The recipe is carried over from spectraxgk-feedstock's recipe/recipe.yaml, which is already in the v1 format. The changes are:

• package name spectraxgk -> gkx, version 1.7.0 -> 1.7.1, and the matching PyPI source URL and sha256
• entry points: upstream collapsed the two console scripts spectrax-gk and spectraxgk into a single gkx = gkx.cli:main
• setuptools >=77 in host, because upstream's pyproject.toml now uses PEP 639 (license = "MIT" plus license-files = ["LICENSE"]) and older setuptools does not emit that metadata
• jaxlib added to run, since upstream declares it directly and pip_check reads the distribution metadata
• solvax is now unbounded, matching the 1.7.1 sdist metadata, which dropped the >=0.7.3,<0.8 bound the old recipe carried (upstream main has since added >=0.12.0, which will flow into the recipe with the next release)
• about summary, description and URLs retargeted at the renamed project: homepage and repository now point at uwplasma/GKX, and documentation moved from spectrax-gk.readthedocs.io to gkx.readthedocs.io

noarch: python, the matplotlib-base dependency, the unconditional tomli, and the pip_check plus CLI smoke test are unchanged from the reviewed spectraxgk recipe.

Once this merges we will open an issue on conda-forge/spectraxgk-feedstock and follow it with an archive request in conda-forge/admin-requests, so the old feedstock stops presenting 1.7.0 as current.

Built and tested locally with rattler-build build --recipe recipes/gkx/recipe.yaml -c conda-forge before submitting.

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated recipe".
• Recipe uses the v1 recipe.yaml format, or this PR explains the exceptional requirement for deprecated v0.
• License file is packaged (see the v1 example recipe for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/gkx/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/gkx/recipe.yaml:

• ℹ️ The recipe sets python_min to 3.10, which is equal or lower than the default provided by conda-forge's global pinning. Please remove the redefinition.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/31213239674. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/gkx/recipe.yaml) and found it was in an excellent condition.

[RKHashmani]

I addressed the linter's python_min hint. The redefinition equal to the global default is removed as suggested.

Windows fails because there are currently no jaxlib builds for win-64.

[RKHashmani]

@conda-forge/help-python, ready for review!

[matthewfeickert]

Looks pretty good beyond some small revisions and needing all maintainers to sign off.

(This is also basically a direct port of https://github.com/conda-forge/spectraxgk-feedstock/blob/7aaf335d4fa426f6b6e61706aafed974b1351fe7/recipe/recipe.yaml which makes it easy 👍)

[matthewfeickert]

LGTM

[matthewfeickert]

@RKHashmani Thanks for contributing your first recipe to conda-forge! If you aren't already, we'd encourage you to join the conda-forge Zulip server to ask questions and engage with the broader community.