When input file paths are HTTP URIs, like the one we can use with vsicurl, the extended filename options deduction can be a mess.
The current implementation only split the filename from the first encountered ? character.
This is wrong, since such character can be part of a HTTP request pointing to an online raster file.
Implementation Details
The new implementation consider that the last occurrence of ?& marks the beginning of the extended filename options.
Classes and files
ENH: Modules/Core/Common/src/otbExtendedFilenameHelper.cxx (new implementation)
FIX: some tests contained wrong extended filename pattern (the documentation clearly states the right pattern is Path/Image.ext?&key1=value1&key2=value2).
