For issue #231, force column size to be determined

[yitam]

Issue #231: When binding params, in the function determine_column_size_or_precision(), column size is set to SQL_SS_LENGTH_UNLIMITED (0). Then later in resize_output_buffer_if_necessary() when calculating the required size, the buffer length is smaller than required, which results in truncation error. This affects not only varchar(max), but also nvarchar(max), varbinary(max), and xml types

[coveralls]

Coverage increased (+1.9%) to 46.369% when pulling 909bcfe on yitam:GH231 into ff25f29 on Microsoft:dev.

[coveralls]

Coverage increased (+1.7%) to 46.129% when pulling aec1c83 on yitam:GH231 into ff25f29 on Microsoft:dev.

[coveralls]

Coverage increased (+1.7%) to 46.137% when pulling aec1c83 on yitam:GH231 into ff25f29 on Microsoft:dev.

[yitam]

The problem described in issue #231 also affects InOut parameters, and for varbinary(max), the encoding is not set properly. The new test will test both output and inout parameters plus these data types with unlimited sizes

[coveralls]

Coverage increased (+0.5%) to 46.661% when pulling 0705d9b on yitam:GH231 into cc925ad on Microsoft:dev.

[coveralls]

Coverage increased (+0.5%) to 46.661% when pulling f7a1c72 on yitam:GH231 into e448281 on Microsoft:dev.