remove streamz git dependency, standardize build dependency names, consolidate some dependency lists

[jameslamb]

Description

Proposes some additional cleanup in dependencies.yaml, for things I noticed while working through #15483.

• standardizes the naming of keys in the files: section for build dependencies
  • py_build_{project} = dependencies for the [build-system] table
  • py_rapids_build_{project} = dependencies for the [tool.rapids-build-backend] table
  • this is how it was done over most of the other repos in Update RAPIDS Python packages to use rapids-build-backend build-planning#31, it was just missed because cudf was one of the first repos to add rapids-build-backend
• removes the dependency on building streamz from latest source on GitHub
  • custreamz conda packages and wheels depend on packages for those, not this git dependency

    • cudf/dependencies.yaml

      Lines 752 to 754 in 2f7d354

      	- output_types: [conda, requirements, pyproject]
      	packages:
      	- streamz

    • cudf/conda/recipes/custreamz/meta.yaml

      Lines 45 to 47 in 2f7d354

      	run:
      	- python
      	- streamz

  • if this is really needed, I don't think it belongs in the build_python_cudf set
  • the last commit to streamz was 2 years ago (https://github.com/python-streamz/streamz), this doesn't seem like a rapids-dask-dependency, try-to-always-test-against-latest, situation to me
  • I'm guessing this is left over from a time before streamz was regularly publishing wheels... it's been in dependencies.yaml since that file was first introduced here in November 2022 (Bifurcate Dependency Lists [skip-gpuci] #11674)
  • the last release, v0.6.4, was made on July 27, 2022. There have been around 20 commits to master since then (history link) ... but if custreamz really needed those, I'd expect custreamz to depend on the version built from GitHub sources. I strongly suspect that that isn't the case.
• removes build_python_cudf and build_python_libcudf lists in dependencies.yaml, in favor of re-using the depends_on_rmm and depends_on_pylibcudf lists

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

Approving in the current state but I have a proposal for further improvement.

[bdice]

I think we can refactor the py_rapids_build_cudf list to include lists named depends_on_rmm and depends_on_pylibcudf rather than specifying those packages here. We already have a depends_on_pylibcudf that we can use, but we should add a depends_on_rmm list. It'd help deduplicate a lot.

That would make build_python_cudf an empty dependency list, which is probably fine.

[jameslamb]

I totally agree! I'm happy to just push that here as well and use this PR for more dependencies.yaml refactoring. It'd help with #15483.

I'll do that and request another review.

[jameslamb]

Ok @bdice I just pushed 8bfbb95, which does the following:

• adds a depends_on_rmm list
• removes build_python_pylibcudf (which only held an rmm requirement)
• removes build_python_cudf (which only held rmm and pylibcudf requirements)
• corresponding changes in files: section (including some reordering so dependency lists are alphabetical)

[jameslamb]

Thanks for the help @bdice ! I'm happy to see this get simplified 😊

[jameslamb]

/merge