[EAK-355] DependsOn: add alternative variations of 'visibility' action

[liubou-masiuk]

Usecase 1: a field needs to be simultaneously non-submittable and hidden (or submittable made visible) depending on some condition
Usecase 2: a field needs to be cleared (but still submittable) when it is hidden

As a toolkit user
I want to be able to perform such actions easily

Ideas:

1. add two new "alternative" actions (Usecase 1 action can be called "Active", but other suggestions are, of course, welcome)
2. add "modes" to the current visibility action ("disable", "clear", etc). This option may be too verbose

[liubou-masiuk]

Per @ala-n

1. consider splitting into 2 tickets
2. there is a POC of the first option, we can consider adding it to dependsOn
3. the second action can be implemented with fieldName@Delete SlingostServlet command

[ala-n]

According to the latest discussion, this possibility is going to be resolved by the possibility of using multiple elementary actions per query, see:

• [EAK-473] DependsOn: ability to pass multiple actions per query (POC) #473
• [EAK-356] DependsOn: Add "inversed" shortcuts for "disabled" and "required" actions #356