Memory profiling

[themighty1]

This PR adds the functionality to profile memory usage of the native prover.
The gh workflow ran successfully here https://github.com/themighty1/tlsn/actions/runs/11553800582

This PR is a copy of #602

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.48%. Comparing base (c6dc262) to head (f9fa5e3).
Report is 1 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #658   +/-   ##
=======================================
  Coverage   54.48%   54.48%           
=======================================
  Files         193      193           
  Lines       20618    20618           
=======================================
  Hits        11234    11234           
  Misses       9384     9384           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sinui0]

Please be sure to squash the commits and add @valo as a co-author

[heeckhau]

Looking good!

[themighty1]

I added a Co-authored-by: line but apparently github didn't pick it up. Sorry for that.

[heeckhau]

@valo Thanks again for your great contribution 🙏

[valo]

Oh no... no attribution in the git history 😢 A friendly recommendation to avoid this, as it will drive external contributors away. For example, I'll prob avoid making new contributions here from now on.

[themighty1]

@valo , do you know what your Co-authored-by: line should look like (for future reference)
Im sorry that there was a chain of mishaps: you were not able to respond to my request here #602 (comment)
Then I waited for a week and decided to move forward. Then I tried to find your "Co-authored-by:" line in your previous commits, but I couldn't find it. Lesson learned.

We actually do encourage contributors and even go out of the way to atrribute their contributions.
Your future contributions are very welcome.

[valo]

Im sorry that there was a chain of mishaps: you were not able to respond to my request here #602 (comment)

For some reason the emails for this issue were going to my spam folder :-( On the top of this, I was attending some events and not paying attention to GitHub that much. I should have paid more attention to this.

Co-authored-by: Valentin Mihov <[email protected]>

[themighty1]

@valo , thanks
#660
is the best we could come up with. You are attributed now, albeit in a non-straightforward manner.