[BUGFIX beta] contextualizeBindingPath should be aware of empty paths
[FEATURE propertyBraceExpansion] Ensure __ember_observes__ is set properly.

The refactor in 5d95885 to allow only the declarative form of expansion
caused the `__ember_observes__` property to be unset when the feature
was enabled.

This was identified while fixing the Travis asset publishing and build
failures in #3863.

@twokul / @rjackson

/cc @hjdivad
Merge pull request #3875 from rjackson/fix_propertyBraceExpansion_prototype_expansion

[FEATURE propertyBraceExpansion] Ensure __ember_observes__ is set properly.
Merge pull request #3870 from marcioj/3860_fix

contextualizeBindingPath should be aware of empty paths
Do not allow overwriting of controllers proxy properties

It was possible to accidentally set the value of `controllers.foo`, where
foo is a container-retrieved controller value as specified using `needs`.

There is no case where a developer would want to do this on purpose, and
it can cause confusion. This commit throws an error when this occurs.
render helper with context, now creates the controller
with its model, rather than setting the model post creation.

Setting the context post creating causes unneeded and wasteful change events.

@hjdivad & @stefanpenner
Merge pull request #3871 from lukemelia/read-only-needs

Do not allow overwriting of controllers proxy properties
remove Ember.alias as it has been deprecated since 2013-01-08
Merge pull request #3880 from stefanpenner/remove-ember-alias

remove Ember.alias as it has been deprecated since 2013-01-08
Merge pull request #3878 from stefanpenner/fix-render-helper

render helper with context, now creates the controller
Optimizes `{{#unbound if}}` and `{{#unbound unless}}`.

They no longer create useless metamorph views and generally execute
less code. There is no public API change here, just optimization.

Props to @machty for the review and help.
Merge pull request #3881 from lukemelia/unboundif

Optimizes `{{#unbound if}}` and `{{#unbound unless}}`.
[FEATURE Composable Computed Properties]

This feature allows you to combine (compose) different computed
properties together. So it gives you a really nice "functional
programming" like syntax to deal with complex expressions.

Example:
```javascript
var sort    = Ember.computed.sort,
    union   = Ember.computed.union,
    equal   = Ember.computed.equal,
    mapBy   = Ember.computed.mapBy,
    not     = Ember.computed.not,
    compare = Ember.compare,
    and     = Ember.computed.and;

var Person  = Ember.Object.extend(
               napTime: and(
                          equal('state', 'sleepy'),
                            not('thirsty'),
                            not('hungry')
                          )
              );

var person = Person.create({
               state: 'sleepy',
               thirsty: true,
               hungry: false
             });

var Kitties = Ember.Object.extend(
       allKitties: sort(
               union(
                 mapBy('whiteKitties', 'name'),
                 mapBy('blackKitties', 'name')
               ),
               compare
             )
      );
var kitties = Kitties.create({
        whiteKitties: Ember.A([{
                                 name: 'whiskeys'
                               }, {
                                 name: 'bagels'
                              }]),
        blackKitties: Ember.A([{ name: 'little boots' }]),
       });

person.get('napTime') => false
person.set('thirsty', false)
person.get('napTime') => true

kitties.get('allKitties') => ['bagels', 'little boots', 'whiskeys']
```

Kudos to brilliant @hjdivad for his help.

updating benchmark.js to the latest version

adding benchmark as a node dev dependency
adding jquery.js for old benchmarking tests
adding a stub test for computed properties
adding distold to .gitignore

moving files to old folder

adds benchmark files

adds benchmark and microtime to package.json

WIP commit, adding benchmark.js for benchmarking

adding lodash, benchmark dep

using es6 modules and grunt to run benchmarks

Not breaking benchmarking suite, no tests yet.

moar stuff

first running benchmark tests

adds more benchmarking for ember

adds benchmarking UI

adds colors and options to disable console logging

UI and benchmark improvements

moar benchmarks

updated canary

rebasing and updating ember with ccp
wip; tests pass

behind a feature flag now
wip;

works with POJOs
hackin on benchmarks; they need lots more work
first stab at fixing benchmarks
fixed benchmarks for CCP and CP get comparison
make jshint happy
adding errors UI table