Create "Ingest and analyze profile data" section in docs

[aleks-p]

Changes:

1. Reorder top level items
2. Add a new top level item "Ingest and analyze profile data"
3. Move "profiling types", "analyzing profiles" and "profile cli" to the new section
4. Minor improvement to the profile CLI docs

[Rperry2174]

can we explicitly write out the defaults so that people copy-pasting are aware of how and what format to change the time frame for something like this ?

[Rperry2174]

also is this really "merging" or just querying?

for example if I query data from 12:00 to 12:45 and I merge data from 12:00-12:45 isn't that the same thing?

[aleks-p]

can we explicitly write out the defaults so that people copy-pasting are aware of how and what format to change the time frame for something like this ?

Done!

also is this really "merging" or just querying?

for example if I query data from 12:00 to 12:45 and I merge data from 12:00-12:45 isn't that the same thing?

We call it "merge" throughout the codebase because we are (potentially) merging data from multiple profiles into one. I agree that it is a confusing word, merge is often used for mutating operations (e.g., git merge).

I don't think we can call it just query here since we have two subcommands (merge and series) but we could call it query profile potentially (with the risk of confusion about whether it returns data from one or more profiles). I'll leave it as it is for now though to avoid a breaking change at this time.

[knylander-grafana]

I did some minor updates to this content--mostly just fixing headings and some formatting. Let's get this approved so we can work on the introductory material. Some o f the content on Analyze profiles will move to the introduction content.