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
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