Reland "Record allocation stack traces"

This is the exact copy of r17365 which was reverted in r17488 due to memory corruption. The root cause for the memory corruption - missing check for bump pointer limit before storing filler map must be addressed in r17626 where allocation hooks were removed from the generated code and left only in the runtime.

This is initial implementation of allocation profiler.

Whenever new object allocation is reported to the HeapProfiler and allocation tracking is on we will capture current stack trace, add it to the collection of the allocation traces (a tree) and attribute the allocated size to the top JS function on the stack.

Format of serialized heap snapshot is extended to include information about recorded allocation stack traces.

This patch is r17301 plus a fix for the test crash in debug mode. The test crashed because we were traversing stack trace when just allocated object wasn't completely configured, in particular the map pointer was incorrect. Invalid Map pointer broke heap iteration required to find Code object for a given pc during stack traversal. The solution is to insert free space filler in the newly allocated block just before collecting stack trace.

BUG=chromium:277984, v8:2949
R=bmeurer@chromium.org

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

[yurys, 2013-11-14 10:49:18]

Benedikt, please take a look.

[Benedikt Meurer, 2013-11-14 11:21:55]

LGTM

[yurys, 2013-11-14 12:13:37]

Committed patchset #1 manually as r17742 (presubmit successful).