feat(profilin): Add explanation for lockstep sampling (#11885)

We had this odd sampling frequency value in our docs which looks like a typo but it is not. This PR adds a note box to reassure the readers with some explanation and a reference link to why.

Author: BYK

develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx

@@ -295,6 +295,21 @@ stack ID.
 You should collect samples at a frequency of 101Hz, or roughly once every 10
 milliseconds.
 
+<Alert title="Note" level="info">
+The 101Hz number above is not a typo. It is intentionally slightly off from 100Hz to avoid a condition
+named "lockstep sampling" where the profiling samples occur at the same frequency as a loop in the
+application. Ideally, the samples should be much more frequent than any cycles in the application, or
+at random intervals, so that the chance it occurs in any particular operation is proportional to the
+amount of time that operation takes. But this is often not feasible, so the next best thing is to use
+a sampling rate that doesn't coincide with the likely frequency of program cycles. 
+
+We also chose 101 for its primality, whereas 1 below 100–99–is evenly divisible by several 
+smaller numbers, which could lead to similar lockstep behavior.
+
+This explanation is an excerpt from [this awesome StackOverflow answer](https://stackoverflow.com/a/45471031/1181370)
+which has more details and a nice analogy for the issue.
+</Alert>
+
 `samples`
 
 : *List, required* Contains a list of sample object captured during execution.