feat: profiling on web

[kirillzyusko]

A second PR that actually implements profiling and saves profiles as file.

Pretty important findings:

• even though we can specify sampling interval -> OS will ignore an interval below a threshold. On windows machines it's 16ms, on unix machines - it's 10ms. In this PR I specified sampling as 10ms - on windows 16ms will be automatically used.
• when profiling is enabled (as I can understand when specific header is returned) then it automatically adds 1-3% of overhead);

Android	Web

An example of profile (Hermes format):

trace-2024-06-25T08_42_59.123Z.cpuprofile.txt

An example of the converted file:

trace-2024-06-25T08_42_59.123Z.cpuprofile.txt-converted.json

[hannojg]

even though we can specify sampling interval -> OS will ignore an

lets make sure to add that to the jsdoc comments + maybe document it in the readme (once we add a we b section!)

[hannojg]

@kirillzyusko do we need in the package json some pointer to the web index file?

[kirillzyusko]

@hannojg hm, I don't think so. I've tested on the app, and we consume module folder from lib and if we run on web then automatically index.web.js file is used, so I don't think it's needed here 🤔