Support per-configuration visibility conditions

#### Summary
Some properties are directly related to other properties. Meaning, the state of one property determines something about another property. In this case here, `Treat warnings as errors` determines if one property can be shown (`Treat specific warnings as errors`) versus showing another property (`Exclude specific warnings as errors`). It works like a light-switch, when it is off, you see `Treat specific warnings as errors`, and when it is on, you see `Exclude specific warnings as errors`.

However, there is a problem. `Treat warnings as errors` can be varied by Configuration. Meaning, each configuration variation (`Release`, `Debug`, etc.) can have their own value for this light-switch. If one is off and one is on, you'll see both `Treat specific warnings as errors` and `Exclude specific warnings as errors`. The relationship to which variation those apply is the problem.

Each of these properties are, therefore, able to be varied by Configuration. But the UI doesn't display this properly. Firstly, it does not automatically go into `Vary value by Configuration` mode. This means, it shows a single edit box instead of one edit box per Configuration variation. If you switch it to `Vary value by Configuration` mode, it will show Configurations for which this value does not apply! This adds to the confusion. The ask here is to make dependent properties (those whom depend on other properties to be visible) to automatically react to varied parent properties.

#### Expected Behavior
| Before | After
| ----------- | -----------
| Going from this state, all variation values of the parent property are the same [unchecked]. | To this state [checked], will properly show varied UI for dependent properties. I've make a mock-up here.
|  | 

#### Actual Behavior
| Before | After | Additional
| ----------- | ----------- | -----------
| Going from this state, all variation values of the parent property are the same [unchecked]. | To this state [checked], does not show variation UI for dependent properties. | Additionally, enabling variation UI for dependent properties improperly shows variations that are not applicable for those properties, given the parent property's state.
|  |  | 

#### Clip of Suggestion