[EAK-457] Add field-level MSM inheritance for authoring dialogs

[liubou-masiuk]

Currently, the user can only lock/unlock MSM inheritance on the whole component. Sometimes there is a need to do it for just 1-2 fields and leave the inheritance on the rest of the component

There is a POC of this solution that is based on field-level inheritance in page properties. it can be adapted and released as an open-source solution

Assumptions:

• field level inheritance will work closely with DependsOn and we will assume that DependsOn is always installed together with field-inheritance

Risks:

• need to review the overrides we've made for Granite to enable field-level MSM, try to understand if we can do without them or perhaps change them to something less dangerous

Questions:

• this feature needs to be optional for the end-user. how can we turn it off (presumably by adding/not adding inheritance markers on dialog fields)? how will it be configured by the toolkit users?