Add DKX (renamed from sfincs-jax)

[RKHashmani]

This adds a recipe for dkx, the renamed continuation of sfincs-jax (existing feedstock: https://github.com/conda-forge/sfincs-jax-feedstock). Upstream renamed the project from sfincs_jax to DKX and now develops it at https://github.com/uwplasma/DKX. PyPI sfincs-jax stops at 1.2.0 and PyPI dkx continues from 2.0.0, so conda-forge currently has no path forward for this package under the old name.

The recipe is carried over from sfincs-jax-feedstock's recipe/recipe.yaml, which is already in the v1 format. This is a nearly pure rename; the changes are:

• package name sfincs-jax -> dkx, version 1.2.0 -> 2.0.0, and the matching PyPI source URL and sha256
• entry points: upstream collapsed sfincs_jax into a single dkx = dkx.cli:main
• import test and CLI smoke test renamed accordingly (dkx, dkx --help)
• about homepage and repository retargeted at uwplasma/DKX; documentation stays at sfincs-jax.readthedocs.io, which is where upstream's pyproject.toml still publishes the renamed project's docs (dkx.readthedocs.io belongs to an unrelated project)

The dependency set (jax, numpy, scipy, h5py, netcdf4, matplotlib-base, solvax), noarch: python, and the pip_check test are unchanged from the reviewed sfincs-jax recipe, matching upstream's unchanged runtime metadata.

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

Built and tested locally with rattler-build build --recipe recipes/dkx/recipe.yaml --variant-config <python_min pinning> -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/dkx/recipe.yaml) and found it was in an excellent condition.

[RKHashmani]

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 the latest release. Are any older releases needed as well?

[RKHashmani]

This is the latest release. Are any older releases needed as well?

Not that I'm aware of.

[matthewfeickert]

LGTM