Lock API refactoring

Description

Initial situation:
--------------------------------------------------------------
The existing Lock API must be refactored due to insufficient extensibility, usability and functionality.
--------------------------------------------------------------

Actual behavior:
--------------------------------------------------------------
The current Lock API implementation is component based and was implemented within the concerned components (table and form).
Due to the fact that a Lock API should be data record concerned, the reference should be made to implement Locking based on a data record type (for example VirtualTableRows)
--------------------------------------------------------------

Expected behaviour:
--------------------------------------------------------------
Lock API has to be based on a specific data set type (VirtualTableRow).
.. .. clearly separated from UI-Components
.. .. VirtualTable server communication based.
.. .. Lock Strategy extensibility.
.. .. Lock Messaging/Monitoring Strategy extensibility.
.. .. Easy to trigger from API-User side too.
--------------------------------------------------------------

Comment:
--------------------------------------------------------------
The refactoring process includes JavaDoc...
--------------------------------------------------------------

Environment

None
Fixed

Assignee

JW

Reporter

JW

Labels

None

Epic/Theme

None

Affects versions

Priority

Blocker