Bug22: Can't retrieve data from Chronozoom

1. Current code assumed a given GUID as the timeline head. Changed to use first timeline with no parent.
2. This fix required to add the "ParentTimeline" property to the Timeline entity, which modified the name of a SQL field. This caused deployment to fail in databases already deployed since a upgrade behavior was not defined. Therefore, entity upgrade behavior was also added with this change. The current behavior allows dropping data (if required) to perform a schema upgrade.
3. Added commented connection strings to enable data migration to work with SQL Azure and local deployments to use SQL Server.

This fix has already been verified and closed by a-chumagin, see: https://github.com/alterm4nn/ChronoZoom/issues/22