Support xs:int for WFS feature properties.

xs:integer is an unbounded integer whereas xs:int is a signed 32 bits integer.
see : http://stackoverflow.com/questions/15336872/xsd-what-is-the-difference-between-xsinteger-and-xsint
The interpretation of what an xs:integer is can vary depending on the implementation. For example
Microsoft's System.Xml.Schema.XmlSchemaDataType.ValueType maps xs:integer to System.decimal
and xs:int to System.Int32
see : http://bytes.com/topic/net/answers/172493-xmlschemadatatype-xs-integer-system-decimal

This code change will remove any ambiguity when the property is known to be an int32.
Update mapwfs.c
Fix undeclared symbols in maputil.c

Getting the following build error, I think the fix is to use MS_TRUE and MS_FALSE.

    /tmp/mapserver/maputil.c: In function ‘msEvalTextExpressionJSonEscape’:
    /tmp/mapserver/maputil.c:685:54: error: ‘TRUE’ undeclared (first use in this function)
    
    /tmp/mapserver/maputil.c: In function ‘msEvalTextExpression’:
    /tmp/mapserver/maputil.c:690:54: error: ‘FALSE’ undeclared (first use in this function)
Merge pull request #4940 from pagameba/patch-1

Fix undeclared symbols in maputil.c
OGR input: add 2.5D support when USE_POINT_Z_M is defined
PostGIS input: add 2.5D support when USE_POINT_Z_M is defined

Consequently the PROCESSING option FORCE2D is assumed to be NO by
default when USE_POINT_Z_M is defined (related to #4803)
OGR output: fix export of line geometry as MultiPoint
GML output: export XYZ when USE_POINT_Z_M is defined and gml_geomtype is set to Point25D/LineString25D/etc.. (same syntax as 2.5D OGR output)
Autotest: build with WITH_POINT_Z_M=1
Update msautotest
Merge pull request #4936 from mathieudugal/patch-1

Support xs:int for WFS feature properties.
PostGIS input: fix regression introduced by 62d3e61 when dealing with 2D-only PostGIS 1.X geometries (#4941)
Merge branch 'master' of github.com:mapserver/mapserver
OGR output (zip form): when we have FORMATOPTION "FILENAME=basename.ext.zip", use basename.ext as the name of the OGR datasource (#4933)
Update msautotest to latest rev (https://github.com/mapserver/mapserver/issues/4933)
OGR output: add wfs_additional_files_in_output layer/web metadata item (#4884)
Merge branch 'master' of github.com:mapserver/mapserver

Conflicts:
	msautotest
#define GEOS_USE_ONLY_R_API to avoid accidental use of non reentrant GEOS API
Fix illegal use of stack-allocated objects in maprendering

pointObj and lineObj defined in the else block in msDrawLabelBounds()
are valid only in the "else" block context. Once outside (e.g. in the
"return msDrawShadeSymbol()"), the variables should not be considered
valid anymore ; it led in some cases in underlying calls to
msSmallAlloc() with a negative integer, resulting in a "unable to
allocate memory" error.

First version of this patch extracted the pointObj / lineObj variables
just before the "if" call, the current one was proposed by @gberaudo.
Merge pull request #4952 from pmauduit/fix-illegal-use-stack

Fix illegal use of stack-allocated objects in maprendering