* Add "Speeding up V8 heap snapshots" blog post.

Co-authored-by: Rob Palmer <rpalmer57@bloomberg.net>

Several fixes in accuracy, specially related to NODE_OPTIONS processing,
coming from the code review. Also some writing improvements.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

When we tried to make the post less Node.js specific, we want a bit
too far, as the parts related to --heapsnapshot-near-heap-limit are
indeed Node.js specific. Provided more clarity on that.

…ation

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

The level of details in teh source position caching fix explanation
was quite poor, not even explaining why the source line position was
not cached. Expand it after proposal from Joyee Cheung.

In previous version, we talked about "unoptimized development JS" and
"optimized production JS", that could be misleading, as Joyee Cheung
pointed out, because it could induce reader to think about JS runtime
optimizations.

So this change removes reference there to optimized/unoptimized JS to
later detail how production source code is optimized using bundling
and minification.

In the original description, we wrongly state that the heap limit is
set by V8 to be 1400MB. Instead of this, it was an application
specific limit.

Also clarify that, in the test case, hitting Out-Of-Memory would hint
there was a leak.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

Many insightful improvements to the writing of heap snapshot optimizations blog post, that can be landed altogether.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

"And old friend" reference was for the ETW fix that I presented in a different blog post that is not even linked. And it is redundant as later I explain that this issue is similar to another one fixed in ETW.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

The images in the v8 heap snapshot optimizations post were too much
big, with lots of empty space that was not relevant and made it harder
to read the contents. After cropping the images, not it is more
focused on the information that matters.

Co-authored-by: Shu-yu Guo <syg@chromium.org>

Manually apply suggestions that could not be applied directly from
the GH UI.

…vestigation

Following @syg recommendation, avoid explicit engineers reference
while explaining the procedure to investigate the performance problem.

V8 team is not sponsored. Work is actually done by engineers of
different companies. Rewrite the credits section accordingly.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

…previous post

Originally the blog post was part of a series until it was proposed
to be an independent post in v8.dev. Make the reference to the
previous post independent of the fact by referring to the link of
the previous post.

…mplified writing

Several changes to reduce redundancies and simplify reading the
post:
- Remove step-by-step guide of using Windows Performance Recording,
referring to upstream documentation now.
- Snippets are now almost C++ code instead of pseudocode.
- Some typos.
- Simplified line break caching explanation, and removed reference
to equivalent ETW fix.

Co-authored-by: Shu-yu Guo <syg@chromium.org>