[DevTools] Add utils for perfomance marks

[jstejada]

Summary

When rebasing my profiling PR (#22167) I encountered a lot of merge conflicts, so I figured it might make sense to provide similar utils for performance marks, both to make it easier to manage my merge conflicts, but also a lot of the branching introduced into the code.

Just a proposal, so let me know if you think this makes sense, but also totally fine to abandon this refactor.

Test Plan

• yarn flow
• yarn test
• yarn test-build-devtools
• manual test of browser extension

[bvaughn]

I'm generally a fan of this change. Seems like the resulting code is more readable.

The one nit I find myself thinking about is the naming of these functions. The naming pattern of "withAsyncPerformanceMark" feels slightly odd to me. The purpose of these functions is to measure code, so maybe something like "measureAsyncCode" / "measureSyncCode" would read more naturally?

This is a super nit though. Feel free to ignore if you disagree.

[lunaruan]

Yay refactoring for code quality! 😃

[jstejada]

bikeshedding: for context, the reason i used the with* naming is kind of to indicate that i'm "wrapping" it in something, in this case performance marks. using a name that's a verb like measureSyncCode or something makes me think that we're returning a measurement, or something of that sort, but also not a big deal