[test] Add back lsan leak detection

tools/memory/lsan/suppressions.txt

Index: tools/memory/lsan/suppressions.txt
diff --git a/tools/memory/lsan/suppressions.txt b/tools/memory/lsan/suppressions.txt
new file mode 100644
index 0000000000000000000000000000000000000000..36e59ecd5108b87cb461fbc44cd4ff5ae728d707
--- /dev/null
+++ b/tools/memory/lsan/suppressions.txt
@@ -0,0 +1,19 @@
+# Do not add new suppressions below.
+# TODO(machenbach): Delete this file as soon as it is empty.
+
+# cctest

[Alexander Potapenko, 2017/01/31 14:34:11]

Are there bugs filed for these suppressions? If so, please add bug IDs here to
ease tracking them.

[Michael Achenbach, 2017/01/31 14:55:37]

Nope, there's only the one issue attached to the bug. There should be max 2-3
root causes I think. I'll pass the bug around until they're all fixed.

+leak:v8::internal::Debug::NextAsyncTaskId
+leak:v8::internal::wasm::DecodeWasmModule
+leak:v8::internal::wasm::WasmInterpreter::WasmInterpreter
+leak:v8::internal::WasmDebugInfo::SetBreakpoint
+
+# debugger
+leak:v8_inspector::WasmTranslation::TranslatorImpl::DisassemblingTranslator::AddFakeScript
+leak:v8::internal::compiler::JumpThreading::ApplyForwarding
+
+# mjsunit
+leak:v8::internal::FuncNameInferrer::FuncNameInferrer
+leak:v8::internal::JSArrayBuffer::SetupAllocatingData
+
+# unittests
+leak:v8::internal::Isolate::FindOrAllocatePerThreadDataForThisThread