Gap of Negative Duration could NOT be Fixed - AW Server stuck in loop without exiting

- [x] I am on the [latest](https://github.com/ActivityWatch/activitywatch/releases/latest) ActivityWatch version.
- [x] I have searched the issues of this repo and believe that this is not a duplicate.

- **OS name and version**: Arch Linux x86_64
- **ActivityWatch version**: v0.13.2

## Describe the bug

Within one specific week I am getting:
```
2025-01-07 06:06:55 [WARNING]: Gap was of negative duration but could be safely merged (-165.163s). This message will only show once per batch. (aw_transform.flood:46)
2025-01-07 06:06:55 [WARNING]: Gap was of negative duration and could NOT be safely merged (-330.409s). This warning will only show once per batch. (aw_transform.flood:52)
```
the query will run out of time and the banner
`AxiosError: timeout of 90000ms exceeded. See dev console (F12) and/or server logs for more info.`
is displayed at the top of the webpage. However the activitywatch server will still continue to use 100% of one CPU core until manually stopped.

## To Reproduce

I start the server
The server is running
I can change to the previous week, no problem
Note the cpu load on the right, the spike occurs when I change the week, but its okay, because the calculation is finished after some time.
Now if I change to the week before that the CPU load does not decrease
At some time a timeout message is displayed and a warning in the logs
But even though the request is supposed to time out, the CPU usage stays at 100%
Pressing Ctrl C does not do anything
But sending SIGTERM works

## Expected behavior

Just seeing the stats of that week
## Documentation

Logs:
[aw-log-bug.log](https://github.com/user-attachments/files/18328030/aw-log-bug.log)

## Additional context

Maybe related to #239