Cleanup scripts for databases should consider incomplete orders

Current Situation

• The following cleanup scripts to purge databases are provided with the JobScheduler Master's ./bin directory:
  • cleanup_jobscheduler_tables.cmd | .sh
  • cleanup_reporting_tables.cmd | .sh
• The scripts can be parameterized for the number of days for which the logs and history of tasks and orders should be retained, earlier entries are removed from the database.
• If a user runs the scripts for a tight interval, e.g. purges the database for a 3 days interval and if the lifetime of running ad hoc orders exceeds this period, e.g. due to a "suspended" state for more than 3 days, then such orders cannot be removed with the JOC Cockpit operation to delete orders.

Desired Behavior

• The cleanup scripts should not consider orders for which the current order run is not completed. This could be represented by order states such as "suspended" or "waiting_for_resource". History entries for orders that did not complete their current run are not removed from the database.