Mitigate "Timestamp is in the future" error

[slaweet]

When user's OS time is a few seconds ahead, all transactions are rejected with "Invalid transaction timestamp. TimeStamp is in the Future" error message.

When this error is obtained in lisk-js, it could try to do the transaction again with timestamp 10 seconds in the past. Maybe try to repeat this step 3 times with 10, 20, 30 seconds?

There are several issues on Lisk Nano reporting this: LiskArchive/lisk-nano#485 LiskArchive/lisk-nano#458 LiskArchive/lisk-nano#365
I heard even more on Lisk Chat, so I consider this to be a big problem. It happens mainly on Windows due to its lack of time sync.