Add View _behaviors reference to the associated behaviors

Views should have a private reference to their associated behaviors. We initially avoided keeping this reference because accessing it in production code is an anti-pattern, but there are a couple reasons why we should have it.

1. internal properties like _events, _ui are super common. 
2. clean up our `behaviors` wrapping logic which we do in Behaviors now, but could do in view methods
3. debugging 
4. testing
5. dev tools 
Super nitpicky, but drop the `have`, so it reads nicer?