Take into account AREA_OR_POINT metadata for GeoTIFF images
The geoTIFF format provides 2 ways of describing the raster space : http://geotiff.maptools.org/spec/geotiff2.5.html GDAL correctly handles those two ways since 3.2.0. (see : https://github.com/opengeospatial/ogcapi-coverages/issues/92)
In OTB 7.x, the metadata key AREA_OR_POINT was read in the keywordlist allowing GDAL to determine if a shift has to be applied on the GCP position. This metadata key was written on the output image, so input and output images had the same raster space.
In OTB 8.0, this metadata is not read, thus the output images always have a default value for AREA_OR_POINT (Area, as described in gdal documentation), instead of taking the value from the input image. This causes problems because GDAL now makes a differences between the two modes, which results failing tests due to a difference of AREA_OR_POINT between the baseline and the tests, leading to shifted GCPs.
- Add "AREA_OR_POINT" key in otbMetadataKey
- Read it in GDALImageIO
- Write it in GDALImageIO
- Update the baseline => cherry-pick the commit d20ac1c13dc14c2be4cc14c965709d2e6e648957 from release-7.3