fix typo in computed_macros.js

change 'provied' to 'provided' to improve API doc readability.
Merge pull request #5468 from chriskohlbrenner/master

[DOC] fix typo in computed_macros.js
Remove isContainer flag
[BUGFIX release] Allow for bound property {{input}} type.
Merge pull request #5469 from mmun/remove-is-container

Remove isContainer flag
Merge pull request #5470 from rwjblue/allow-dynamic-type

[BUGFIX release] Allow for bound property {{input}} type.
Update CHANGELOG for 1.7 and 1.8.0-beta.1.
Post release version bump.
Fix typo ("period if time" to "period of time")
Merge pull request #5472 from chesterlaw/patch-1

Fix typo ("period if time" to "period of time")
Generated documentation updates.

* Adds `RSVP` back (via `bower_components/` directory).
* Remove `container` (this is considered private API).
* Remove `metamorph` (it is not used anymore).
* Remove `loader` (there are no docs and it is not public API).
* Add `ember-routing-handlebars`.
Merge pull request #5474 from rwjblue/enable-rsvp-in-docs

Generated documentation updates.
Prevent extra method.toString checks.

It appears that the intent here was to only check the
`method.toString().indexOf('_super')` once, and store the result so that
we do not need to check the same method twice, but we were never actual
storing `__hasSuper` on the method so it was just always going to check
the `toString`.
Merge pull request #5480 from rwjblue/prevent-extra-toStrings

Prevent extra method.toString checks.
String.prototype.indexOf returns -1 for non-matches.

Previous check would wrap everything (unless `_super` was at position
`0` which is not possible).
Merge pull request #5481 from rwjblue/properly-use-indexOf

String.prototype.indexOf returns -1 for non-matches.
Pass depKey and old/new value to will/didChange

Until now, when a property is set, we were passing to [did|will]Change
only the object and the name of the property.
This information is very limited for some uses.
I can be very handy by example to know inside didChange the old value of
the property.
Similarly, it can also be useful to know the new value inside willChange
When the didChange is triggered by changes in a dependency, we might also
need to know which dependency changed.

All this information was available in the `set` method, so now those
values are propagated all the way thought `iterDeps` until didWill change.
I've figured out a hacky way of testing this.