E2E guide how to collect a dump and debug it with VS or LLDB

[mikelle-rogers]

Walkthrough: see #515

[mikelle-rogers]

@hoyosjs what method of collection were you thinking we should use for this doc issue? (collecting a dump on a crash, using dotnet-dump, gc-dump, etc.)?

[hoyosjs]

I'd mention the other guides - essentially make this a quick tutorial pointing to the more detailed guides. For this I'd use a sample app that crashes and then load it into LLDB, since I feel like that's a scenario that's interesting and we don't have too much information floating around on.

# How to analyze a dump

## Collecting a dump

Share pointers to 

- dotnet dump for hang or ad-hoc dumps
- Collecting dumps under a debugger (VS and WinDBG)
- Collecting crash dumps with the env vars.
- Perhaps point to procdump on the sysinternals page.
- Point to Unix system dumps with the caveats that not everything might work.

## Analyzing a dump

Explain how to analyze it using lldb, link sos commands. There's some prior art in here: https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-linux-dumps#analyze-dumps-on-linux

## Alternatives

Link to https://learn.microsoft.com/en-us/visualstudio/debugger/using-dump-files?view=vs-2022#BKMK_Open_a_dump_file and https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump#using-dotnet-dump and the caveats (when to recommend one vs the other)

[tommcdon]

Closing via dotnet/docs#32988