Improve LogCleanupCommand to keep configured execution time when using NextRun parameter

[martinweiler]

When scheduling a LogCleanupCommand with NextRun=1d, the actual execution time for the next run is calculated as (current command execution time + nextRun value). Over time, this can lead to the scheduled execution time to slip, ie. a job scheduled initially at 00:00 gets executed at 00:10, and the execution could be outside of a designated maintenance window.

The expectation is that subsequent executions happen at the defined start time + nextRun value, ie. a job scheduled initially at 00:00 with NextRun=1d should always run at 00:00, regardless of how long it takes to execute it.

[martinweiler]

@elguardian could you please review this PR: kiegroup/jbpm#2292
Thanks!

[martinweiler]

Scheduled for inclusion in 7.13.4 / 8.0.4: https://issues.redhat.com/browse/RHPAM-4750

[martinweiler]

Closing, fixes merged:

• upstream: [kie-roadmap-119] Scheduled jobs do not keep configured execution time kiegroup/jbpm#2292
• 7.67.x-blue: [7.67.x-blue] [kie-roadmap-119] Scheduled jobs do not keep configured execution time kiegroup/jbpm#2308

[YajieY]

RHPAM-4750 has been in the bamoe-8.0.4 fixed issues list & ready to release.