Integrate UW Read API with MSU Client Improvements

Currently the ChronoZoom client interacts with the temporary MSU Read API. This change performs the initial integration to switch the ChronoZoom client to use the Read API provided by UW. Details follow:

- ChronoZoom.Entities: Mostly, alignment with the new API document naming conventions(lowercase and adding the start/end fields).

- ChronoZoom.UI: Aligns the Read API to the API document retrieving a single timeline and using the LCA.

- ChronoZoom.UI/Dumps: Modified the fields to new API conventions + improve JSON formatting.

- ChronoZoom.UI/NewScript: Modified to point to the new API (not the temporary one)

- ChronoZoom.UI/Script: Modified to comply with the new naming conventions.

Two outstanding issues that still need to be fixed (Both of which MSU is already working on):

1) Content Items not loading: The server currently retrieves timelines WITH content. We need the client to support this. At some point, it would be good to split content from timelines; however, if the server provides more information, the client should be able to handle it. 

2) Humanity Timelines render Incorrectly: This is caused by a mismatch in time definitions. The client is assuming that year 0 is 2013 while the new API assumes that year 0 was 2013 years ago. The right approach here is to modify the client to move year 0 back 2013 years.