Logseq timer calculations are incorrect when enough seconds push the timer over 1h

I found a bug where the time sum is not displayed correctly under certain conditions.

If the sum of the minutes is less than 60, and the sum of the seconds is enough to push the timer over 60 minutes, the result is incorrect.

The result is only correct when the minutes are enough to be more than or equal to 60.

See Timed Test Task A in my example below, 20m + 19m + 20m = 59m. Less than 60.
However the seconds 30s + 30s + 1s push the timer over or equal to 60 minutes. Logseq doesn’t understand this and just shows 1s as the result.

Timed Test Task B is showing an example where Logseq understands that an hour has passed, as 20m + 20m + 20m is equal or greater than 1h. So no bug there.

Timed Test Task A is the bug and requires a fix.

Also, please ignore the start/finish times as they are for record keeping and it seems Logseq does not use those values.

- TODO **Timed Test Task A:** This one shows a time of `1s`. This is incorrect.
  :LOGBOOK:
  CLOCK: [2022-01-07 Fri 00:00:00]--[2022-01-07 Fri 00:00:01] =>  00:20:30
  CLOCK: [2022-01-07 Fri 00:00:02]--[2022-01-07 Fri 00:00:03] =>  00:19:30
  CLOCK: [2022-01-07 Fri 00:00:04]--[2022-01-07 Fri 00:00:05] =>  00:20:01
  :END:
- TODO **Timed Test Task B:** This one shows a time of `1h1s`. This is correct.
  :LOGBOOK:
  CLOCK: [2022-01-07 Fri 00:00:00]--[2022-01-07 Fri 00:00:01] =>  00:20:00
  CLOCK: [2022-01-07 Fri 00:00:02]--[2022-01-07 Fri 00:00:03] =>  00:20:00
  CLOCK: [2022-01-07 Fri 00:00:04]--[2022-01-07 Fri 00:00:05] =>  00:20:01
  :END: