Improve supportability

## Summary

This is about tools which will help with investigations:
- How to simplify investigations for support representatives
- Tools to help with memory dump analysis
- Export Fiddler-style traces from the server

### People with context about this

@davidfowl, @shirhatti, @jkotalik, @halter73

Also talk to CSS folks about what is needed.

## Motivation and goals

1-2 paragraphs, or a bullet-pointed list. What existing pain points does this solve? What evidence shows it's valuable to solve this?

## In scope

A list of major scenarios, perhaps in priority order.

## Out of scope

Scenarios you explicitly want to exclude.

## Risks / unknowns

How might developers misinterpret/misuse this? How might implementing it restrict us from other enhancements in the future? Also list any perf/security/correctness concerns.

## Examples

Give brief examples of possible developer experiences (e.g., code they would write).

Don't be deeply concerned with how it would be implemented yet. Your examples could even be from other technology stacks.

Start with the issue summary and review the proposed investigation areas: support-representative workflows, memory dump analysis, and Fiddler-style server trace export. Seek context from the people named in the issue and CSS stakeholders, then document motivation, scope, risks, examples, and a design. Done means the proposal has clear goals and consensus on its direction.

Written by the indexing model from the issue text.