Handle case where client time has drifted further than 500ms after we have saved the server time offset

[marto83]

It's a continuation of spec item (RSA4b1). Once we have saved the server time we should check if the client time hasn't drifted further. In this case we should call and get Server time again

┆Issue is synchronized with this Jira Story by Unito

[sacOO7]

Two solutions were proposed based on the internal discussion ->

1. comparing it with UTC time on local (Need to validate if UTC time changes when the user changes time for a clock .. it should be same on all computer irrespective of set time)
2. starting a stopwatch, to keep track of drifted time (if a client changes it manually), if it drifts by +/-500 ms, mark token as expired.

[sacOO7]

According to recent findings, it seems the first solution is already in place. I will try to implement it using the second solution.