Disallow GeoSeries from accepting a column in favor of _from_column

[mroeschke]

Description

closes #1433

Mirroring the upstream cudf changes in rapidsai/cudf#16454, cudf.Series disallows accepting a ColumnBase in favor of the cudf.Series._from_column constructor. This PR does the same for GeoSeries as well as addresses the breakages due to the upstream cudf change.

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]

Question: are cudf.Series._* methods considered private? If so, it makes me nervous to add more private cudf access in cuspatial.

[bdice]

Question: are cudf.Series._* methods considered private? If so, it makes me nervous to add more private cudf access in cuspatial.

I don't think there is an alternative path here. Previously, constructing a Series from a column was not a code path that we intended to be public, but it worked. @mroeschke took that away to reduce the abuse of the Series constructor. If I understand the plan correctly, in the future all the code using columns (private internals of cudf) should be moved to use pylibcudf where columns will have a stable public API. That public API is not yet ready, to my knowledge. In the interim, this PR will be necessary to unblock cuspatial.

[bdice]

Looks like some CI tests are failing:

FAILED tests/test_transform.py::test_geoseries_input - TypeError: data type 'geometry' not understood

[bdice]

/merge