fix: log gdal stderr instead of raising an exception TDE-557

[paulfouquet]

Description

stderr from gdal should not be interpreted as an error. When gdal is on error, it returns an exit code <> 0. This behaviour is already captured by subprocess.run (with check=True) raising a subprocess.CalledProcessError in a case of "a non-zero exit status". Any stderr should be Warnings or other messages <> error.

Change

Log a warning instead of raising an exception when gdal stderr is not empty