remove uneeded normalization (lookupFactory already does this)
Merge pull request #5497 from stefanpenner/remove-wasteful-normalize

remove uneeded normalization (lookupFactory already does this)
[BUGFIX release] Makes sure that internal properties do not leak onto created objects.

Fixes #5485.
Merge pull request #5501 from twokul/super-fix

[BUGFIX release] Makes sure that internal properties do not leak onto created objects.
Use svg instead of png to get better image quality
Merge pull request #5508 from PeterDaveHello/patch-1

[DOC] Use svg instead of png to get better image quality
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 did/will change.

The info of the change is also pased for array dependencies.
In this kind of changes, the only information I have is the numbed of values
added, but not the actual elements being added.