add more common variations of `Ember.Object.create`

[stefanpenner]

• internal objects (views/ember-data models) go down a non-default fast-path to above the overhead of Object.defineProperty
• there is also a perf difference between the first instance for a given class, and the nth. (benchmark hits both)

[stefanpenner]

Interesting aside, looking at how various configurations of test runs cause widely different metrics.

The reality is:

1. realistic code into many edge-cases, resulting in a hard-to reach steady state.
2. Some individual bad paths, can "poison" others quite easily
3. Short of code-gen, it is quite unclear how to mitigate the above in systems where a kernel (ember) calls out to dynamic user code)

with components:

without components:

With only non-enumerable:

[eviltrout]

Thanks!