Make sure ExternalCallbackScope is always created when VM state changes to EXTERNAL

Make sure ExternalCallbackScope is always created when VM state changes to EXTERNAL

ExternalCallbackScope is used to let CPU profiler know which API callback is being executed. Whenever such callback is called we should create VMState<ETERNAL> and ExternalCallbackScope. This patch fixes several places where VMState<ETERNAL> went without ExternalCallbackScope.

BUG=244580
R=dcarney@chromium.org, svenpanne@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=15249

[yurys, 2013-06-14 13:03:01]

This change uses THREADED_PROFILED_TEST macro introduced in
https://codereview.chromium.org/17072002/

[dcarney, 2013-06-14 17:38:42]

lgtm

I was originally going to remove the various Call functions after cutover from
the old callbacks is complete, but it looks like you've found a good use for
them.

[Sven Panne, 2013-06-17 12:02:24]

LGTM if neither the v8 perf bots nor the Chrome perf bots show any kind of
regression.

[yurys, 2013-06-20 14:47:48]

Committed patchset #6 manually as r15249 (presubmit successful).