The consequence of sharing the same GDAL object and protecting them under mutex is that
instanciating a new pipeline for job preview background can actually be blocked for
a long time, and thus causing the UI to be totally non-responsive

So change the strategy to use a global cache of GDAL datasets that can be reused by
cloned GDAL providers, while still maintaining the number of opened datasets to
a reasonable amount.