Multiply seconds timestamp from chain by 1000 to convert to milliseconds

[glitch003]

This PR multiplies the timestamp from chain by 1000 to convert it to milliseconds, since that's what the JS date constructor needs.

I discovered this by adding additional logs (since removed, but was in this commit 830bc2c) and you can see the result from a run below. The tokenExpiresDate is wrong because it expects timestamps in milliseconds, and we passed one in seconds, resulting in a date of 1970-01-21T00:53:16.800Z.

timestamp from contract 1731196800                                                                                                                                                                                                 
tokenExpiresDate { TZDate 1970-01-21T00:53:16.800Z timeZone: 'UTC', internal: 1970-01-21T00:53:16.800Z }                                                                                                                           
tomorrow { TZDate 2024-11-03T00:44:49.827Z timeZone: 'UTC', internal: 2024-11-03T00:44:49.827Z }                                                                                                                                   
today { TZDate 2024-11-02T00:44:49.827Z timeZone: 'UTC', internal: 2024-11-02T00:44:49.827Z }

[MaximusHaximus]

👍 Good catch