Config: apply type coercion, at least for integer based values

[fallwith]

We have some configuration parameter value type coercion logic parked in the lab branch which is a) passing all CI tests, b) received dev approval, and c) passed csec tests for known integer handling issues.

Our CI suites involve lots and lots of iterations that completely flush and entirely reinitialize all agent configuration and layering in type coercion does have a performance impact that is easily seen in a CI context. Before merging the type coercion logic in, we'd like to be absolutely sure that the performance hit is expected to be slight outside of a CI context.

As a fallback plan, we should at least incorporate integer focused coercion for the csec agent's benefit.

[workato-integration]

https://new-relic.atlassian.net/browse/NR-336421