The View helper learns about the container

This provides more options to allow for a global free code base.

```javascript
// stays the same
{{view App.FuView}}

// uses the container
{{view 'fu'}}
```

The following continues to work as it does today, looking directly up on the view, rather then via the container. but leads to some annoying internal conditionals, and maybe ambiguity
```javascript
{{view 'view.someOtherView'}}
```


To deal with this, i believe the forward moving goal is as follows:
```javascript
// current
{{view 'view.someOtherView'}}
// future
{{view view.someOtherView}}
```

The question is how do we move forward.

1. support both string and non-string lookups, detect 'view.' and spew deprecation warnings
2. error hard on string lookups that prefix with 'view:'
3. don't detect the view case, merely allow the existing "your view is missing error" to handle it.

Let the discussion begin.