New STAC Catalogue Friendly User Testing - feedbacks from implementation

I am using the Python library `pystac_client` to search for Sentinel-2-l2a items. I know from the old STAC API that there is a limit of 10 000 tiles. Running the following snippet 

```

import pystac_client
import numpy as np

catalog = pystac_client.Client.open("https://stac.dataspace.copernicus.eu/v1")
items = list(
    catalog.search(
        collections=["sentinel-2-l2a"],
        bbox=[0.0, 40.0, 20.0, 60.0],
        datetime=["2020-07-01", "2020-08-01"],
    ).items()
)
print(len(items))

```

gives 6387 items, which just works fine. To see what happens when a search request hits the limit of 10 000 tiles, I tested running 

```

import pystac_client
import numpy as np

catalog = pystac_client.Client.open("https://stac.dataspace.copernicus.eu/v1")
items = list(
    catalog.search(
        collections=["sentinel-2-l2a"],
        bbox=[0.0, 40.0, 20.0, 60.0],
        datetime=["2020-07-01", "2020-09-01"],
    ).items()
)
print(len(items))

```

Which ends out in an infinite loop without exiting the code. 

I find stac items in the senitnel-2-l2a collection, which do not link to any data. E.g. the item https://browser.stac.dataspace.copernicus.eu/collections/sentinel-2-l2a/items/S2B_MSIL2A_20201201T105419_N0500_R051_T30TXQ_20230302T211406?.language=en&.asset=asset-B02_60m does not have any data, when clicking on thumbnail. 

Following the documentation on https://documentation.dataspace.copernicus.eu/APIs/S3.html#example-access-using-s3cmd to download the jp2 file

```bash

s3cmd -c ~/.s3cfg get s3://eodata/Sentinel-2/MSI/L2A_N0500/2020/12/01/S2B_MSIL2A_20201201T105419_N0500_R051_T30TXQ_20230302T211406.SAFE/GRANULE/L2A_T30TXQ_A019525_20201201T105442/IMG_DATA/R60m/T30TXQ_20201201T105419_B02_60m.jp2

```

results in 

```

ERROR: Download of './T30TXQ_20201201T105419_B02_60m.jp2' failed (Reason: 404 (NoSuchKey))

ERROR: S3 error: 404 (NoSuchKey)

```

Maybe it would be better to exclude these items where observation tiles are not available. 

At collection level, there is an issue with the summaries:

"summaries": {
"gsd": [10],
"platform": ["sentinel-2a","sentinel-2b"],

The gsd should be a list of 10, 20, 60.
I guess the collection should also include sentinel-2c.

It was agreed with ESA to report only the best available resolution.

I found a Sentinel-2 L2A tile (https://stac.dataspace.copernicus.eu/v1/collections/sentinel-2-l2a/items/S2A_MSIL2A_20220131T102251_N0400_R065_T32UNB_20220131T133159) with asset's hrefs following the form "s3://DIAS/...". However I do not find any directory with the name"DIAS". Exchanging "DIAS" with "eodata" solves the issue. 

This STAC item may be corrected. 

I found items for Sentinel-2 L2A with incorrect bounding box. It happens for tiles which cross the anti-meridian. See the following STAC items:   https://stac.dataspace.copernicus.eu/v1/collections/sentinel-2-l2a/items/S2A_MSIL2A_20220228T230531_N0400_R044_T60UXB_20220301T012127, https://stac.dataspace.copernicus.eu/v1/collections/sentinel-2-l2a/items/S2A_MSIL2A_20220509T230541_N0400_R044_T01UBS_20220510T021512. 

I get these items for the search parameters (bbox=[10.379305295420469, 51.03524986614165, 10.524829317544002, 51.12337186389743], time-range=('2016-11-01', '2024-12-31')), because the bounding box if the above mentions items span from -180° to +180°. 

It seems that the search using filter in the Sentinel-1 Ground Range Detected (GDR) collection using the "Product Type" shows a list of possibilities in the STACBrowser (queryables) not matching the product type inside the metadata.  See https://browser.stac.dataspace.copernicus.eu/collections/sentinel-1-grd?.itemFilterOpen=1 (comment by YC (Spacebel).