[tracing] Introduce MemoryDumpArgs to enable light and heavy dumps

gin/v8_isolate_memory_dump_provider_unittest.cc

Index: gin/v8_isolate_memory_dump_provider_unittest.cc
diff --git a/gin/v8_isolate_memory_dump_provider_unittest.cc b/gin/v8_isolate_memory_dump_provider_unittest.cc
index b1693cdf062fc7583f1bf4c3aa9227b7e2471e6a..46d512bd8925b20835b1c80a2080c1e63e60779c 100644
--- a/gin/v8_isolate_memory_dump_provider_unittest.cc
+++ b/gin/v8_isolate_memory_dump_provider_unittest.cc
@@ -23,8 +23,10 @@ TEST_F(V8MemoryDumpProviderTest, DumpStatistics) {
 
   scoped_ptr<base::trace_event::ProcessMemoryDump> process_memory_dump(
       new base::trace_event::ProcessMemoryDump(nullptr));
+  base::trace_event::MemoryDumpArgs dump_args = {
+      base::trace_event::MemoryDumpArgs::LEVEL_OF_DETAIL_HIGH};
   instance_->isolate_memory_dump_provider_for_testing()->OnMemoryDump(
-      process_memory_dump.get());
+      dump_args, process_memory_dump.get());
   const base::trace_event::ProcessMemoryDump::AllocatorDumpsMap&
       allocator_dumps = process_memory_dump->allocator_dumps();