Xcube-cci

* Allow reading of datasets that do not specify chunk sizes (e.g., FIRE)
[Cate 1033](https://github.com/CCI-Tools/cate/issues/1033).

* Ensure compatibility with xarray >= 0.20.2 and python >= 3.10
* Ensure compatibility with expected odp update

* Always show time bounds as coordinate, not as data variable
* Prevent IndexError when requesting data with a time range

* Fixed issue where opening datasets in a daily resolution without a delimiting
time range would cause memory errors
[56](https://github.com/dcs4cop/xcube-cci/issues/56).

* Fixed issue that datasets with spatial bounds could not be opened.
* Show version as `__version__`
* The interface of the method `search_data` of the CciOdpDataStore
has been changed. Search parameters `ecv`, `frequency` `institute`,
`processing_level`, `product_string`, `product_version`, `data_type`,
`sensor`, and `platform` may now be passed in a dictionary parameter named
`cci_attrs`. This makes it possible again to use the parameter `data_type`
[54](https://github.com/dcs4cop/xcube-cci/issues/54).

* Version 0.9 now requires xcube 0.9 because of incompatible API changes in the
xcube data store framework.
* CciOdpCubeOpener has been removed.
* CciOdpDatasetOpener and CciOdpDataStore now have a new constructor parameter
`normalize`, that may be used to apply normalization steps to the CCI
datasets.
* Set coordinates correctly. All coordinates are present in data descriptions
and opened datasets, no coordinates appear as data variables
[42](https://github.com/dcs4cop/xcube-cci/issues/42).
* CRS are supported correctly. CRS variables are present in datasets in case
the CRS is different from 'WGS84', the CRS information is provided by the
data descriptor [50](https://github.com/dcs4cop/xcube-cci/issues/50).