Document policy for StrictMode violations when using opentelemetry-android #1188
Description
When all the options are turned on for Android's StrictMode, starting the Android agent will trigger violations like disk reads on the main thread due to what it is doing as well as what the underlying OTel Java SDK is doing.
These fall into three buckets: 1) could be avoid; 2) could be bypassed at the cost of lost functionality; and 3) in practice, something we have to do (i.e. either because it's unavoidable or costly to do so).
Having some documentation in place that spells out exactly how the existing violations can be bypassed and what can't, and what you have to do the former, will be useful when questions like this comes up.
At the end of the day, it may not be realistic to make the default use case of these packages to be completely StrictMode violation-free, but our policy towards them should be known and documented.