[continuous-profiler] inaccurate sampling interval on Windows

[lachmatt]

Bug Report

Symptom

Describe the bug
Default timer resolution on Windows is 15.625ms.
Due to that, thread samples are collected less frequently than requested (e.g. every 31.25ms instead of 20ms requested by the plugin).

Additional context

One of the options to increase timer resolution is to set it using timeBeginPeriod. This seems to be used by e.g. runtime's own sampling profiler.
There are some downsides to increasing timer resolution, as described in runtime's repository and in this blog post, but I think they are acceptable for this project.

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[nrcventura]

I would like to know if there is really a need for a sampling interval more frequent than 16ms before we take the time to adjust settings that can affect the whole system. It would also be good to know how a more frequent sampling interval can affect the performance of the application. Until we have a clear need, I'm leaning towards just documenting this as a limitation.