Duplicate timer creation in multi-node setup

In a setup with multiple kie-server nodes, the following sequence of actions can lead to duplicate EJB timer instances getting created:

1. Start a process instance containing a timer on node1
2. Access the newly created process instance on node2 (eg. REST call to retrieve variables)

If the call in step #2 happens before the EJB timers are synced at the EAP layer (wait time < refresh-interval), then RHPAM will create a second EJB timer instance during the session initialization.

 
Note: this issue is similar to the scenario tracked in JBEAP-22092, but for a slightly different use case.