Update Dependency List with dependencies.yaml [skip gpuci]

[isVoid]

Description

This PR updates dependency lists with dependencies.yaml.

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]

Style checks should not be dependent on a specific Python version being specified in the matrix (if no value is specified, the matrix match will fail). The Python requirement in the build list should be sufficient. However, we may want a default (empty matrix in the last entry) of py_version defining >=3.8,<3.10 instead of putting it in build.

Suggested change

- py_version

[isVoid]

Any reason doing it just for py_version? Why not also cython?

[isVoid]

And are you suggesting removing python entry from build and use py_version in all?

[bdice]

I think you did what I wanted -- remove py_version from the style check dependency list.

As for removing python from build -- is there a C++ library that can be built without Python? If so, I would remove python, cython, ... from build and put them in a separate list like build_python. We're trying to achieve a level of modularity/granularity that is useful for minimizing dependencies at each stage of a build.

[galipremsagar]

Suggested change

	- cmake>=3.23.1
	- cmake>=3.23.1,!=3.25.0

[ajschmidt8]

I would have expected libcudf and librmm / rmm in this list, too? Avoid making those transitive dependencies if cuspatial directly relies on them via #include or cimport. (If it is only imported in Python, it is a runtime and not a build time dependency.) Also combine this advice with my other comment to split out the C++ and Python build dependencies (we have yet to do this for cudf, still work in progress).

@bdice, I just pushed some changes. I'll defer to you to add these necessary dependencies. Otherwise, I think this PR looks good to me!

[bdice]

@ajschmidt8 Feel free to merge if you think this is ready, then we can start the GitHub Actions migration. I checked the current CI workflows and I think we have already handled all the features that the cuSpatial repo will need.