feat: add dependency-groups recipe

[henryiii]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here 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.

This is the official package for PEP 735, and is needed for conda-forge/nox-feedstock#37.

I've tried using ratter-build for it.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/dependency-groups/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/dependency-groups/recipe.yaml:

• ❌ The homepage item is expected in the about section.

For recipes/dependency-groups/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the run section of recipe, you should usually use python >=${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13243993340. 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/dependency-groups/recipe.yaml) and found it was in an excellent condition.

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

For recipes/dependency-groups/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the run section of recipe, you should usually use python >=${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13244116227. 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/dependency-groups/recipe.yaml) and found it was in an excellent condition.

[henryiii]

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

[henryiii]

@sirosen, let me know if you want me to add you to the feedstock maintainers for dependency-groups. Also, pypa/pip#13065 looks like it was approved but has conflicts.

nox is now updated on conda-forge using the new package. :)

[sirosen]

Let's leave me out of the conda side unless it's useful to have multiple people with privileges.
I've hardly used conda, so I'm not in a good position to know what I'm doing! 😁

Thanks for letting me know that some conflicts have appeared -- I'll get that ironed out. Based on discussion in that PR, I think we're on track to have pip {install,download,wheel} --group support in 25.1 in a few months! I'll do my best to keep the PR healthy until it merges.