check if 3.10 successful before merge

[eroell]

PR Checklist

• This comment contains a description of changes (with reason)
• Referenced issue is linked
• If you've fixed a bug or added code that should be tested, add tests!
• Documentation in docs is updated

Description of changes

Technical details
There is a very strange error going on, occasionally in the Ubuntu 3.10 tests, and the Ubuntu 3.11 pre-release tests:

FAILED tests/preprocessing/test_highly_variable_features.py::test_highly_variable_features - ehrapy.io._read.IndexNotFoundError:
Could not create AnnData object while reading file /home/runner/work/ehrapy/ehrapy/ehrapy_data/dermatology.csv .
Does index_column named patient_id exist in /home/runner/work/ehrapy/ehrapy/ehrapy_data/dermatology.csv?

The error is related to the dermatology.csv file, read in here

ehrapy/ehrapy/data/_datasets.py

Lines 330 to 362 in 0ee5c21

	def dermatology(
	encoded: bool = False,
	columns_obs_only: dict[str, list[str]] | list[str] | None = None,
	) -> AnnData:
	"""Loads the Dermatology Data Set
	More details: http://archive.ics.uci.edu/ml/datasets/Dermatology
	Preprocessing: https://github.com/theislab/ehrapy-datasets/blob/main/dermatology/dermatology.ipynb
	Args:
	encoded: Whether to return an already encoded object
	columns_obs_only: Columns to include in obs only and not X.
	Returns:
	:class:`~anndata.AnnData` object of the Dermatology Data Set
	Examples:
	>>> import ehrapy as ep
	>>> adata = ep.dt.dermatology(encoded=True)
	"""
	adata = read_csv(
	dataset_path=f"{ehrapy_settings.datasetdir}/dermatology.csv",
	download_dataset_name="dermatology.csv",
	backup_url="https://figshare.com/ndownloader/files/34179300",
	columns_obs_only=columns_obs_only,
	index_column="patient_id",
	)
	if encoded:
	infer_feature_types(adata, output=None, verbose=False)
	return encode(adata, autodetect=True)
	return adata

Quite flaky, only pops up sometimes when repeating the tests

Additional context

[eroell]

how even

[eroell]

Seems to work now again - everywhere. Close for now, hopefully no one will ever need to search for this, and if so, this PR with the posted error will pop up