incubator-kie-issues#2307 data-isolation by process id and version pair

[jstastny-cz]

Fixes:

• Compact architecture persistence layer leaks data between apps connected to single relational database incubator-kie-issues#2307

Part of ensemble:

• incubator-kie-issues#2307 data-isolation by process id and version pair incubator-kie-kogito-runtimes#4302
• incubator-kie-issues#2307 data-isolation by process id and version pair #2337

Broad changes to accommodate for possible filtering of DB entries by process id and version pairs. Important aspect is that the engine was currently not properly populating the version information throughout the internal models, so there are excessive changes related to this, while the actual data-isolation filtering is small footprint.

Moreover, for sake of properly isolate items belonging to reusable subprocesses, id and version information needs to be exposed also for root process, so via root process id and root process version.

Areas affected:

• Data Events - data events were refactored to properly set the new fields, instead of adding yet another constructor with way too many parameters, I implemented builder pattern for the data event objects. This should be now the encouraged way, I have marked the existing multi-parameter constructors as deprecated.
• Database queries - actual database queries are being composed dynamically and depending on local processes, appropriate filtering is appended and parameters bound.
• Conditional enabling of this feature by passing or not Processes bean to Repository class implementations.

Components isolated:

• data-index storage
• embedded jobs addon storage

Components planned in a follow-up PR (for sake of reducing size):

• data-audit storage

[martinweiler]

@jstastny-cz my apologies that I caused the conflict in JPAQuery by merging PR#2328. Once you have resolved this, we should be good with this PR as well. Great work!