Document 'ideal' workflows in gapid docs

If I look at the [Capturing a Trace page](https://gapid.dev/trace/), the page tells me _how_ to capture a trace, but doesn't make any suggestions on what I should do for certain scenarios.

It would be awesome if the docs had some suggested workflows to use when tackling certain issues.

- Debugging a rendering artifact?
- Capture a single frame at the time the artifact is observed
- Capture multiple frames at the time the artifact is observed
- Crash during startup?
- Trace from beginning

Something like that. Maybe some of this exists somewhere assuming there were some public GAPID presentations.