Bug: scope.$.snapshot would only cascade to one level of parents

Another failed correction when changing the includeParents property from false to true
Change: when a value function prefix is set, don't remove other functions from the snapshot

They aren't dangerous, we won't call them, and the developer put them in the scope, so I see no reason to remove them. This leads to questions around event handlers being removed.
scope.$.snapshot changed to not remove $ prefixed properties. scope.$.model added which does

This is because it is important to be able to check for the existence of the $ prefixed properties in an apply, such as:

<button ct-on="doNext" ct-show="doNext">

This ends up making more sense.

scope.$.model only returns properties which are considered "model" properties and replaces the old uses of snapshot.
Example: basic.html which demonstrates the new snapshot change by binding to an event handler for controlling visibility
Null event handlers silently ignored

We throw an exception if the event handler is undefined, but null is just an ignore.
Bug: console detection probably flawed
v0.7.0