Patching memory leak using tracer

[aryanjassal]

Description

This PR will integrate the experimental tracer from js-logger to trace the memory leak to finally patch it. This should make the polykey seednodes stable and robust. This will also act as a live-fire exercise for the tracer.

Issues Fixed

• Fixes Integrate tracer to detect memory leaks #151 (FIX ENG-626)

Tasks

• 1. Integrate tracer into js code
• 2. Integrate tracer into native code
• 3. Replicate memory leak with test/script
• 4. Use tracer to visualise where the leak is coming from

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[linear]

ENG-626

[aryanjassal]

A quick test against object lifecycles and tracer has confirmed that no object is being leaked, although the parent/child relationship is still kind of messed up. I'm working on fixing that right now.