Docs to clarify what various components are used for

[ptodev]

I'd like the new docs to be the place we refer people when someone asks whether the Agent can do something, or whether it can be used in a certain situation with a certain telemetry. We currently don't have a doc which lists all of this info, and we need to rephrase it manually in conversations.

This PR is a draft because I am not sure of the best location for this, and I'm not sure how it is best represented.

[ptodev]

I haven't mentioned some components yet:

• discovery.*
• remote.*
• pyroscope.java
• pyroscope.ebpf
• faro.receiver

I'm worried that this page is starting to get really long. Maybe we could make it a totally separate page?

[clayton-cornell]

I would start with the single page in draft and split only if needed. As it is, each section is fairly small

[clayton-cornell]

But... as I read it we are getting really deep with the heading levels. I would suggest we break this off the index and just have it as its own standalone page. That might help reduce the empty heading overload that the current draft has (we should avoid having a heading immediately followed by another heading with no text in between the headings).

[ptodev]

I think the ToC looks nice with the proposed titles:

[github-actions]

This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!