Draft of ES5 fix to Function.prototype.call and apply

ES5 fix to Function.prototype.call and Function.prototype.apply to
 - not wrap values
 - not pass global object if thisArg is undefined or null

This is the first step to fixing bug:
http://code.google.com/p/v8/issues/detail?id=981

BUG=
TEST=

[Martin Maly, 2011-01-05 23:39:09]

This is a draft of first phase of the fix to bug
http://code.google.com/p/v8/issues/detail?id=981 where first we need to disable
passing global object through Function.call and apply if thisArg is
null/undefined. Next step will be fixing the actual library functions to perform
ToObject individually as specified by ES5.

I ran tests on x64, ia32 and arm (simulator) and presubmit.py.

To keep the scope of the change small I didn't go for the full fix to the bug
981 but plan to do that in future patches.

Please add additional code reviewers in case I didn't identify the optimal ones.

Thank you!
Martin

[Martin Maly, 2011-01-06 00:20:55]

It is probably worth mentioning the relevant paragraphs in the ES spec.

15.3.4.3 (Function.prototype.apply)
15.3.4.4 (Function.prototype.call)

have changed between ES3 and ES5.

In ES3:
If thisArg is null or undefined, the called function is passed the global object
as the this value.
Otherwise, the called function is passed ToObject(thisArg) as the this value.

In ES5 the algorithm changed to not apply ToObject nor to substitute global
object for null or undefined. The note from the ES5 spec (15.3.4.3 and
15.3.4.4):

NOTE The thisArg value is passed without modification as the this value. This is
a change from Edition 3, where a undefined or null thisArg is replaced with the
global object and ToObject is applied to all other values and that result is
passed as the this value.