Log SPAM: error reading MTD_MSIL1C.xml

[jdries]

Users are being misguided by scary error logs that can be disregarded:

Error reading from S3: endpoint: data.cloudferro.com, bucket: EODATA, NoSuchKeyException, key: Sentinel-2/MSI/L2A/2016/01/25/S2A_MSIL2A_20160125T110332_N0201_R094_T30TVP_20160125T110536.SAFE/MTD_MSIL1C.xml
asset with ID/title IMG_DATA_Band_B04_10m_Tile1_Data not found in feature /eodata/Sentinel-2/MSI/L2A/2016/01/18/S2A_MSIL2A_20160118T111402_N0201_R137_T30TWN_20160118T111405.SAFE; inserting NODATA band instead

They are caused by corrupt products from an older processing baseline (201), while a newer 5.x version is already available. Hence not being able to read these products is not an issue.
So we probably need to detect this case, and silently ignore the products rather than logging the error message.

Example job id: j-2409025bdf714eb5a8b53130ee6376bc