TEST: Don't check node id and volume value at initialization response
CrasAudioHandler calls InitializeAudioState() twice on power up
sending 2 dbus messages to set output volume. However we are not
sure about the order of the 2nd message being sent and the 1st
response being received. In the case that the 1st response is received
after the 2nd message is sent, if we check the node id and volume
against the latest cached values, this check could fail and reset the
initialization flag, causing the 2nd response to trigger volume bar
pop up on UI.
BUG=
649360