Reduce CPU load for datainput setValue calls

Add an additional flag to DataInput setValue API that can be used to indicate whether the incoming value should always be considered a change, or whether runtime engine should be signaled only if the value is different from the currently set value.

Traditionally Datainput has always generated a change signal to runtime regardless of incoming value, because there is no way to know if the targeted property has been changed by animation or another datainput.

Adding this flag makes it possible for the API user to explicitly indicate whether the value change should be forced (default traditional behavior), or whether a change is only generated when datainput value actually changes (where user f.ex. knows that this datainput is the sole controller for the target property).

This can decrease CPU load in projects where for some reason datainputs receive frequent updates, but where incoming value might not actually be different from the previous value (regular communication bus updates etc.)