Enable sklearn 1.2

[kbattocchi]

Fixes #711

[fverac]

Given that we are trying to support multiple sklearn versions with our package, in the future should we consider testing across multiple sklearn versions as well?

Because right now our tests only check if our package works with the latest compatible version of sklearn right?

[fverac]

Should we make a minor update to the cate_treatment_names docstrings which currently say
Available only when the featurizer is not None and has a method: `get_feature_names(feature_names)

Update to something like
Available only when the featurizer is not None and has one of the following methods: `get_feature_names(feature_names) or get_feature_names_out(feature_names)

[fverac]

Should we make a minor update to the cate_treatment_names docstrings which currently say Available only when the featurizer is not None and has a method: `get_feature_names(feature_names)

Update to something like Available only when the featurizer is not None and has one of the following methods: `get_feature_names(feature_names) or get_feature_names_out(feature_names)

Also similar thing in _set_transformed_treatment_names in TreatmentExpansionMixin

[kbattocchi]

Yes, systematically testing against a wider range of dependencies has long been something we've wanted to support, but our test matrix is already quite large. This is perhaps something that would be better addressed by nightly tests, which we could add when moving over to GitHub Actions.

But also note that Python 3.7 support was dropped by scikit-learn a while ago, so we're still testing against scikit-learn 1.0.3 when we run our Python 3.7 tests.

[kbattocchi]

I'm going to defer the docstring updates to a subsequent PR, because there are some additional changes to our name propagation logic that I think would simplify things and which can all go in together.