Server WFS: handle axis orientation

[elpaso]

Fixes #36584

Try to fix the canonical mess with axis order for server WFS-T, I'm following the convention used by GeoServer [1] but I'm not really sure I'm getting this right, there are a bunch of tests with the 4 different ways to specify a srsName I could think of.

The bottom line is that 1.0.0 and 1.1.1 with this patch are behaving the same way:

• EPSG:4326 -> LON-LAT
• http://www.opengis.net/gml/srs/epsg.xml#4326 -> LON-LAT
• urn:ogc:def:crs:EPSG::4326 -> LAT-LON
• http://www.opengis.net/def/crs/EPSG/0/4326 -> LAT-LON

[1] https://docs.geoserver.org/latest/en/user/services/wfs/axis_order.html#wfs-basics-axis

[elpaso]

@rouault what do you think? Did I get this right?

[rouault]

@rouault what do you think? Did I get this right?

It's not an exact science, but what you propose looks good to me

[github-actions]

The backport to release-3_16 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-3_16 release-3_16
# Navigate to the new working tree
cd .worktrees/backport-release-3_16
# Create a new branch
git switch --create backport-41242-to-release-3_16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 c9e50cfd2dc025f681f81f1fb64b15784bb6b6cf
# Push it to GitHub
git push --set-upstream origin backport-41242-to-release-3_16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-3_16

Then, create a pull request where the base branch is release-3_16 and the compare/head branch is backport-41242-to-release-3_16.