fix: fix double division, fix loss of millisecond unit

[confusingstraw]

This PR fixes an issue I introduced in the initial useDate=temporal PR here. The generated code for toTimestamp was dividing the epochMilliseconds twice, causing the date to get truncated to 1970-01-01, so the tests would seem to work for dates.

There was also a bug in how nanos was calculated:

Temporal.Instant
    .fromEpochMilliseconds(instant.epochMilliseconds)
    .until(instant);

since we were deriving the start date from epochMilliseconds, so the remainder only included micro/nanoseconds (milliseconds were always 000).

The PR addresses the first issue by ensuring we only divide once, in the generated seconds code. It fixes the latter by using the built-in Temporal.Instant.prototype.round method to round to the nearest second without needing to do any explicit math.

Lastly, it also updates the tests, as the toStrictEqual check was succeeding even for Instants whose string representations were clearly different, so now we will test against the output string.

[stephenh]

Nice, great idea to use their round method.

[stephenh]

🎉 This issue has been resolved in version 2.8.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v2.8.1

Your semantic-release bot 📦🚀