Refactoring DeploymentCache: introducing DeploymentEntityManager and DeploymentManager. Made DeploymentCache an interface for pluggability

history-level for variable-updates

history reporting done from withing the engine

ACT-1300/HEMERA-2522: moved writing of HistoricProcessVariable to process end event (not on BPMN end event), fixed name of variableValueEquals

ACT-1300/HEMERA-2522: removed inheritance from HistoricProcessVariable (as it does not make too much sense), removed fields now no longer used from table and accordingly removed conditions from HistoricProcessVariableQuery

- Added informations for taskId and callActivityId
- Updated create/upgrade scripts

ACT-1202: Tackled the problem which strangely did not fail on local H2, history entry is created in ProcessDefinitionEntity as well

ACT-1202: Fixed remaining test case and adjusted to write audit log for start event on level "activity"

ACT-1202: Adding events to HistoricActivityInstance, marked old "getEndActivityId" deprecated and added the explanation why

ACT-1136 Add support for intermediate catching message event

ACT-1046: - Added an interface "FailedJobCommandFactory" and an implementation of it "DefaultFailedJobCommandFactory", renamed "DecrementJobRetriesCmd" to "FailedJobListener" to able to configure a delay between retries and amount of retries;
- Added "parseIntermediateCatchEvent()" and "parseBoundaryEvent()" in BPMNParseListener to allow some extensions to these elements (e.g. specify a specific failed job retry logic)

ACT-1091 ACT-1092 ACT-1093 ACT-1094 ACT-1095 Adding persistent event subscriptions providing  support for signal events, event based gateway, compensation and transaction

 - Fixed bug in ManagementService (manual create schema didn't work)
 - Added method in BPMNParseListener

There are some formatting changes also, but they won't do harm to my opinion

ACT-564 Added dueDate to task and history + query on dueDate on/before/after on runtime and historic tasks