Port BindableVisualState

[kazo0]

https://github.com/nventive/Nventive.View/blob/master/doc/BindableVisualState.md

[Xiaoy312]

summary: Provides a set of attached properties for adding custom visual state to a Control.
contract:

VisualStateExtensions
	.Group1State = (string)		// Sets the state to enter for the custom VisualStateGroup
	.Group2State = (string)		// Sets the state to enter for the custom VisualStateGroup 2
	.Group3State = ...
	.Group4State = ...

edit: the ViewDebugger parts has been move into its own issue #332, and will be implemented in a different class

[dr1rrb]

Humm I think that we should not merge booth.

The ViewDebugger is something that should removed in release build like the System.Diagnostics.Debug (and we should probably flag all members with the [Conditional("DEBUG")] attribute (like the Debug class).

[francoistanguay]

Could we still merge into same class but different property named .NameOverride or .DebugName that is available in debug only?

Would be less clutter into single class with similar behaviour

[francoistanguay]

And don't know why we call this a custom state?

[francoistanguay]

Could we still merge into same class but different property named .NameOverride or .DebugName that is available in debug only?

Would be less clutter into single class with similar behaviour

Actually the debug is overkill and is I different from any hard coded property in xaml sinks keep the single bendable property and drop the debugger stuff