Enable FutureWarnings and DeprecationWarnings as errors in cugraph (#…

…4415)

Supersedes #4271

There are some tests and internal usages of APIs that emit these warnings still. I don't know the best way to handle these warnings, but this PR ensures that _new_ `FutureWarning`s and `DeprecationWarning`s will raise an error in the CI

Authors:
  - Matthew Roeschke (https://github.com/mroeschke)

Approvers:
  - Rick Ratzel (https://github.com/rlratzel)

URL: #4415

python/cugraph/pytest.ini

@@ -59,5 +59,14 @@ python_functions =
 
 filterwarnings =
           error:::cudf
+          error::FutureWarning
+          error::DeprecationWarning
+          # TODO
+          ignore:Multi is deprecated and the removal of multi edges will no longer be supported:FutureWarning
+          ignore:The legacy column names:FutureWarning
+          ignore:The include_hop_column flag is deprecated and will be removed:FutureWarning
+          ignore:Calling uniform_neighbor_sample with the:FutureWarning
+          ignore:The with_edge_properties flag is deprecated and will be removed:FutureWarning
+          ignore:This function is deprecated. Batched support for multiple vertices:DeprecationWarning
           # Called via dask. Not obviously addressable in cugraph.
-          ignore:The behavior of array concatenation with empty entries is deprecated:FutureWarning:cudf
+          ignore:The behavior of array concatenation with empty entries is deprecated:FutureWarning