Make datetime consistent for authz expiration (#3706)
Make datetime consistent for authz expiration (#3706)

So I took a quick stab at one possible solution for the authz expiration variance discussed over at community.letsencrypt.org/t/inconsistent-datetime-format-in-some-responses/61452

Golang's nanosecond precision results in newly created pending authz having one expires datetime, but subsequent requests have a different expires datetime due to database storage throwing away fractional second information.

  "expires": "2018-04-14T04:43:00.105818284Z",
...
  "expires": "2018-04-14T04:43:00Z",
I am not a Go expert so there might be some more widely accepted approach to accomplishing the same thing, please let me know if you would prefer a different solution.
lucasallan/boulder,jcjones/boulder,letsencrypt/boulder,jfrazelle/boulder,bmw/boulder,jfrazelle/boulder,jfrazelle/boulder,letsencrypt/boulder,jsha/boulder,letsencrypt/boulder,lucasallan/boulder,bmw/boulder,jsha/boulder,jfrazelle/boulder,lucasallan/boulder,jcjones/boulder,jcjones/boulder,jcjones/boulder,bmw/boulder,jsha/boulder