fix TimeSpan.MaxValue bug

TimeSpan.MaxValue.ToString() = 10675199.02:48:05.4775807

That produces wildly unpredictable results and the blob storage container winds up culling records it should not.  Using DateTime.MaxValue solves that by outputting 12/31/9999 11:59:59 PM instead