If music-app is killed by the OOM handler while playing music, it's player session should continue to live on and info lost during the suspend period needs to be exposed

Once the music-app has a normal app lifecycle there needs to be a mechanism to sync the info lost during the suspend period.

An example scenario:
1) A set of music starts playing
2) The music-app is suspended and put in the bg
3) A set of tracks play
4) The user kills the app (doesn't give it focus again)
5) Music stops and the 'session' has ended (potentially the device could even be restarted)
6) However, we have now 'lost' the tracks that were played we need some mechanism that when we next come back, syncs with us as says hey this set of URLs played while you were away with timestamps when they were played and the new currentIndex

The information we require:
- The list of tracks that were played
- A timestamp of when each track was played
- The new currentIndex

What this information is used for:
- Infographics of the number of tracks played today (this is why we need the list of tracks and the timestamp)
- Dynamic playlists, eg most played, recently played etc (this is why we need the list of tracks)
- Restoring the savedQueue and position (this is why we need the currentIndex)