Issue: incorrect state position on 'player_state_changed' event when connecting to Web Playback SDK device (reporting seconds instead of milliseconds)

[pm-33]

There seems to be an issue with the state position being reported in seconds instead of milliseconds for one of the 'player_state_changed' events that is fired when connecting to the Web Playback SDK device.

There also seems to be an inconsistent state duration being reported on the first 'player_state_changed' event that is fired after a track is changed.

Steps to reproduce:

1. Setup the Web Playback SDK as per the quick start guide @ https://developer.spotify.com/documentation/web-playback-sdk/quick-start/
2. Connect to this Web Playback SDK device with user playback context that is currently in the middle of a track (just not at position 0 for demonstration purposes)
3. On successful connection three 'player_state_changed' events are fired and in the second of these three the state position is being reported in seconds instead of milliseconds (screenshot below)

Expected behaviour:

state position to always be reported in milliseconds

Actual behaviour:

state position being reported in seconds for one 'player_state_changed' event

Spotify JS-SDK - v1.7.1-d2b664d