sos messages should not assume windbg context #2978
Description
If I'm running in the context of dotnet dump analyze, the messages will lead me off track. For example:
> clrstack
OS Thread Id: 0x810 (1)
Unable to walk the managed stack. The current thread is likely not a
managed thread. You can run !threads to get a list of managed threads in
the process
Failed to start stack walk: 80070057
> !threads
Required command was not provided.
Unrecognized command or argument '!threads'
> threads
0 0x07A0 (1952)
*1 0x0810 (2064)
2 0x087C (2172)
3 0x0BD4 (3028)
4 0x0AB8 (2744)
5 0x0B60 (2912)
6 0x0AF4 (2804)
7 0x0408 (1032)
>