ENYO-423: TimePicker: Current Time Does Not Initially Display

### Issue:
Integer Picker now fires a change event after every call to Value Changed (instead of just after calls to next() and previous(), as it was doing before). This resulted in a change event from the meridiem picker wrongly changing hours and minutes 
### Fix:
when the call to updateValue() originates from the meridiem picker, get the value of hours and minutes from this.value, instead of the hour and minute pickers.


Enyo-DCO-1.1-Signed-off-by: Krishna Rangarajan <krishna.rangarajan@lge.com>
I realize this is merged already, but just for the sake of discussion, would it be viable to wrap these setters with corresponding `silence` and `unsilence` calls, to cut down on the amount of events being fired? It seems like we wouldn't be interested in the change events coming from the pickers in this case as we are initiating the value change.