Add a test case for `int("2.0")`

[slott56]

I think this should produce an integer 2 value.

It would be handy for working with source documents in JSON notation where the source document string representations of numbers could include a mixture of number syntax ("2.0") and integer syntax ("0"). It seems awkward to have to provide more complex type conversions like int(double(document["field"])) to deal with irregular string values.

[TristonianJones]

That sounds like a pretty reasonable ask. Thanks for the feature request. Currently our conversion standards are pretty strict, but when the input is a formatted string, then the input is explicitly being coerced into another type and the conversion should be more flexible.

[JimLarson]

Should int(<floating-point-formatted-string>) always be equivalent to int(double(<that-string>))? I.e. should int("2.1") also convert to the int 2? Do you want int("9e2") to yield 900?