Reduce repetition between Timeline in-memory profiler and Chrome Event Trace parser

[bvaughn]

Reduce repetition between Timeline in-memory profiler and Chrome Event Trace parser.

Broken into separate commits:

• Moved the in-memory stack management out of 'profilingHooks.js' and into the new 'TimelineData.js'.
• Update 'preprocessData.js' to also use the new 'TimelineData.js' when parsing Trace Event data.

Builds on top of #23185.

Related to #22529.

[facebook-github-bot]

Hi @bvaughn!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!