fix: trim whitespace when parsing numeric properties

[vlsi]

Motivation and Context

If the value parses after trimming, then it would likely be the one the user wants.

Currently, a trailing whitespace in UI is hard to notice, and it breaks test execution. For instance ThreadGroup.threadNum becomes 0 without any warning, and it invalidates test results.