ENH: generic implementation of ea_wrap_cython_operation

[debnathshoham]

Create a property function to decide what to do for EAs in _ea_wrap_cython_operation for groupby ops.
xref : #43634 (comment)

pandas/pandas/core/groupby/ops.py

Lines 318 to 333 in 439acc9

	@final
	def _ea_wrap_cython_operation(
	self,
	values: ExtensionArray,
	min_count: int,
	ngroups: int,
	comp_ids: np.ndarray,
	**kwargs,
	) -> ArrayLike:
	"""
	If we have an ExtensionArray, unwrap, call _cython_operation, and
	re-wrap if appropriate.
	"""
	# TODO: general case implementation overridable by EAs.
	if isinstance(values, BaseMaskedArray) and self.uses_mask():
	return self._masked_ea_wrap_cython_operation(

[jbrockmendel]

I'm increasingly thinking that doing this right will mean implementing the relevant operations end-to-end on the EAs, e.g. groupby_sum. For e.g pyarrow dtypes or potential GPU/distributed arrays they'd want their own things instead of casting back and forth to use our groupby.pyx code

[rhshadrach]

For e.g pyarrow dtypes or potential GPU/distributed arrays they'd want their own things instead of casting back and forth to use our groupby.pyx code

Ref: #51166 (comment)

we should choose one naming scheme for all these methods instead of three slightly different ones. i.e. either a) shove everything into something like groupby_op or b) explicitly have groupby_foo for each of the relevant methods.

The two options aren't mutually exclusive; we could have groupby_op which dispatches to each groupby_foo. Then EA authors could override groupby_op if that is convenient or groupby_foo if they just want a certain method.