No active tracking after start

After starting tracking it seem that time warrior does not find any entries. Issue seems similar to #146 but seems different as the database file name is correct.

```shell
~ → timew start
Tracking
Started 2024-05-03T16:46:41
Current 41
Total 0:00:00
~ → timew
There is no active time tracking.
~ → timew start test
Tracking test
Started 2024-05-03T16:46:52
Current 52
Total 0:00:00
~ → timew
There is no active time tracking.
~ → timew summary
No filtered data found in the range 2024-05-03T00:00:00 - 2024-05-04T00:00:00.
```

I removed the database files and config files with the same result.
```shell
~ → ls .data/timewarrior/data
 2024-05.data  tags.data  undo.data
~ → rm -rf ~/.data/timewarrior ~/.config/timewarrior
~ → timew start
Create new config in /Users/dakota/.config/timewarrior?
Create new database in /Users/dakota/.data/timewarrior? (yes/no) yes
Tracking
Started 2024-05-03T16:50:44
Current 44
Total 0:00:00
~ → timew
There is no active time tracking.
~ → timew stop
There is no active time tracking.
~ → timew start test
Note: 'test' is a new tag.
Tracking test
Started 2024-05-03T16:50:57
Current 57
Total 0:00:00
~ → ls .data/timewarrior/data
2024-05.data tags.data undo.data
```

Diagnostics:
```shell
~ → timew diagnostics

timew 1.7.1
Platform: Darwin

Compiler:
Version: Apple LLVM 15.0.0 (clang-1500.1.0.2.5)
Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64
Compliance: C++17

Build Features
Built: Jan 16 2024 12:35:02
CMake: 3.28.1
Build type: Release

Configuration
TIMEWARRIORDB: -
Cfg: /Users/dakota/.config/timewarrior/timewarrior.cfg (-rw- 0 bytes)
Database: /Users/dakota/.data/timewarrior (drwx 96 bytes)
$EDITOR: nvim
Color theme: Built-in default
00 01 02 03 04 05 06 07 08 09 10 11 12

Extensions
Location: /Users/dakota/.config/timewarrior/extensions (drwx 64 bytes)
(None)

```

I have been using time warrior on my work computer (also osx) without any issues, but after installing on my personal computer I have not been able to get it to work.

- This is a new install (via brew)
- I am running macOS `14.3.1`
- Python 3.12.3

Reproduce the behavior with the reported `timew start`, `timew`, `timew stop`, and `timew summary` commands on macOS, then inspect how active tracking is written to and read from the database shown by `timew diagnostics`. Done means a newly started interval is recognized by the status, stop, and summary commands.

Written by the indexing model from the issue text.