converterrunner: Do not round values unnecassarily
We pass in the precision when we format the string and the rounding causes internal issues when the value is casted to an int.
Test Plan:
Large queries like 100000000000000000000000000000000000000000$ no
longer produce negative results.
This will still need a more proper fix in the frameworks, but the rounding/toString stuff has almost no autotests, so I am a bit more cautious there ;)
Edited by Alexander Lohnau