[EAK-456] DependsOn: add a communication mechanism for third-party "frameworks" to commuticate with DependsOn about the field state

[liubou-masiuk]

We have encountered cases where DependsOn and other UI mechanisms of field state management (e.g. field inheritance or several nested disabling conditions) are in conflict with each other and update the field state without considering each other. The goal of this ticket is to create a communication mechanism on DependsOn API side.
There are 2 main ideas:

1. extend DependsOn internal API to allow third-party code to register "side-effects" (additional action conditions that are submitted to DependsOn by third-party code)
2. add some kind of a "semafore" property that will register all "actors" that try to disable/enable a field. DependsOn will enable the field only after all actors that disabled it, have requested enabling

the second option seems to be quicker, the first - more flexible.
This ticket blocks #457