Fix validation issue for maxAge greater than 2^31

[manu-st]

If you have a cookie with the maxAge to a value larger than 2^31 it causes the SQL queries updating the expiration date to not validate properly. Now we convert the duration in seconds before passing it to the query.

[mcartoixa]

Sorry for the delay.

So the value oneDay was also incorrect: thanks for fixing that. But if the maxAge of a cookie can be larger than 2^31ms, why can't it be larger than 2^31s too? Do you think you can find a way to fix the code in order to prevent overflows altogether?

[manu-st]

We would need to change the way the function dateadd is used so that we perform the add operation in two steps but I feel this will be too much. Before the fix, the maximum date age was just 24.8 days, now we have 68 years, so this is unlikely to be a problem in practice.