The pseudoClock deviates when the container is paused or process put to sleep

The pseudo Clock used by Drools deviates from the real clock when the process is put to sleep or the container running the process is paused.

We see this message
2023-09-28 21:55:53 820 [Thread-0] WARN org.drools.ansible.rulebook.integration.api.rulesengine.AutomaticPseudoClock - Pseudo clock is diverged, the difference is 316 ms

2023-09-28 21:55:57 184 [Thread-0] WARN org.drools.ansible.rulebook.integration.api.rulesengine.AutomaticPseudoClock - Pseudo clock is diverged, the difference is 18147 ms

Since the clock check happens every 100 milli seconds this message ends up filling the logs.

Should the pseudo Clock be synched with the real clock and also does the effect the temporal use cases of once_within/once_after and timeout.

In the past in CI we had seen that if the the process is starved and doesn't get enough cycles it doesn't fire the rules when the clock deviates.