Better i/o error reporting for ogr utilities when lacking read permissions.

[springmeyer]

Improved error reporting when ogr cannot open a file for read access would improve overall user experience.

For example a rare case where this would be useful is when using ogrinfo to query a file where the user does not have read permissions.

If the user does not have read permissions on a dataset ogrinfo currently only returns:

FAILURE: Unable to open datasource '/path/to/fn.shp' with the following drivers
...

If the problem is read permission a more explicit error would be useful.

This is a potential use case for PostGIS users when running as the postgres user to load data into a postgres database. If they attempt to call ogrinfo on a file and their postgres user does not have read permissions a more explicit error would remind them of the problem.

This is a very minor issue but would improve the ogr utility.

[springmeyer]

I also noticed, just now using the new KML driver, that when ogr2ogr tries to write to a filename that already exists as a folder, it will simply return:

ERROR 4: Failed to create KML file ecoregions.kml.

It makes sense that the ogr2ogr drive cannot overwrite a folder with a file, but it would be great to make this error message more explicit.

[Even Rouault]

In 37089:

Win32 Open(): set VSISetError() if bSetError (refs #2253)

[Even Rouault]

In 37090:

ZIP creation: use VSIFOpenExL() to set VSISetError() (refs #2253)

[Even Rouault]

In 37091:

DXF, GeoJSON, GML, KML, LIBKML, ODS, Shape, XLSX: report operating system error if file creation fails (fixes #2253)

[Even Rouault]

In 37093:

Update expected error for mingw (refs #2253)