Adjust ssl client cache expiration logic to have 1 second wiggle room.

base::Time::Now/subtle::TimeNowIgnoringOverride is syncing to the system time by calling an API that returns a relatively low resolution time from a system API and then interpolates with a higher resolution time.
For instance, if the system clock has a ~16ms resolution, when it syncs to the system clock it can get a value that is actually about to advance 16ms.
Other calls also grabbing a system clock-based time, e.g. BoringSSL, may query it right after it advances and appear to get a time that is in the future relative to our interopolated time.

BUG=985152

Change-Id: Ie7b784533eabc9bcbb82d9158767ac90d6151c15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708516
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Sertay Sener <sesener@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#679192}
2 files changed