Cumulocity SNMP Protocols should allow explicit casting of strings to integer/float

We can currently manually configure a SNMP Protocol component through the Device Management application, which allows us to request a specific OID from a SNMP device, and map it to a measurement (or event/alarm) in Cumulocity. However, if the device sends the measurement value as a string, the Cumulocity REST API rejects the measurement because the measurement fragment only permits integer or floating point values.

Ideally, alongside each OID entry in the Protocol "Component", there would be a tick-box to "force" the value to either integer or floating-point/decimal. The Agent would then implement this.