Fix daylight shift test

[saifalharthi]

This PR contains a simple fix for the failing test in this issue #141

[randallwhitman]

Would it be simpler to choose a time near noon instead of a time near midnight?
Versus, would choosing a different rather-random epoch number, merely change which timezone suffers the test failure?
@saifalharthi

[saifalharthi]

The problem was daily light shifting. It would've been easier to select another random epoch number but we'll still have some problems with respect to other timezones. So, I forced the return date to be converted and formatted to a timezone that has daylight savings and that should work with any epoch number given.
@randallwhitman

[randallwhitman]

So in other words, no what epoch-number we choose, it will be too close to midnight in some time zone.
Thanks Saif.

[randallwhitman]

Any chance of undoing the spurious re-ordering?

[randallwhitman]

Saif - I reviewed TestGeoJsonSerDe looking if it would likely need the same change. It looks like the timezone was addressed in a different manner in that one. Do you think either way is any better or worse than the other?

[saifalharthi]

I will take a look at it

[saifalharthi]

I think the approach in TestGeoJsonSerDe should work out fine. I think since it deals with a default timezone offset it will guarantee a more stable time conversion.

[randallwhitman]

OK, sounds good.

[randallwhitman]

Well, if it works, we can merge now and later think about consistency of timezone handling in that test for EsriJson & GeoJson.