[BUG] Infinite loop during the pagination of search results

[AlexRuiz7]

Describe the bug
During the testing of #180, it was detected a bug on the Command Manager where the code to paginate the search results enters an infinite loop.

[2025-01-14T14:01:20,670][WARN ][c.w.c.j.SearchThread     ] [node-1] Empty hits page, not getting searchAfter values

To Reproduce
Steps to reproduce the behavior:

1. By default, the page length is set to 100. The issue is reproducible by simply indexer >100 commands before the search job is run.

Expected behavior

• Pagination works properly.
• The Command Manager does not enter an infinite loop.

Plugins
Command Manager.

Additional context

#213 (review)

[f-galland]

The bug is triggered even after setting the page size to 2 and indexing more than 2 commands.

[f-galland]

Strangely enough, I'm not able to replicate the issue when running the plugin with a breakpoint within SearchThread.run()

[f-galland]

I was actually able to trigger the bug while running the debugger and noticed the PointInTimeBuilder object changes its reference ID from iteration to iteration.

I think even though the debugger is paused, the timeout of the PIT is still running in the background, and the PIT is regenerated.

[f-galland]

Another interesting bit here is that I see a message from the debugger saying 2 other threads also reached breakpoints, and I've only placed a breakpoint within SearchThread.run(), which should be run in a single thread.