Fix test_intersections.py post cudf refactor

[mroeschke]

Description

closes #1395

pairwise_linestring_intersection, tested in this file, returns a cudf.Column for one of it's arguments and used to_pandas to test it's output. in 24.08, the output of Column.to_pandas was changed to a pandas.Index instead of a pandas.Series so modified the test accordingly

Checklist

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

[harrism]

failing doxygen build due to warnings. Weird that this hasn't happened before?

[trxcllnt]

It looks like import cudf is now calling getDeviceCount(). Was this recently changed in cuDF? I don't recall needing a GPU just to import cudf?

[wence-]

It looks like import cudf is now calling getDeviceCount(). Was this recently changed in cuDF? I don't recall needing a GPU just to import cudf?

No. cudf has done validation like that by default since approximately forever (e.g. https://github.com/rapidsai/cudf/blame/070953239a72a669d9f53f48efd85960ac70c381/python/cudf/cudf/__init__.py). See also rapidsai/cudf#4827

[bdice]

Rerunning CI seems to have fixed the issues. This is blocking CI for other PRs, so I will merge it.

[bdice]

/merge