400 errors from client_perf API

After the computer wakes up from sleep, calls to the client_perf API return a 400 error with a detailed_error of report is outdated: timestamp. The reason for this is that most browsers don’t keep the monotonic clock (performance.now()) ticking when the computer is asleep. See for more information.

To fix this, we can either find a way to have the timestamp code to compensate for that drift or we could possibly disable the check for out-of-date reports since we don’t actually use the report timestamp outside of that currently