[APM Go] clarify profiling pages for Go Tracer v2

[hannahkm]

What does this PR do? What is the motivation?

Clarifies profiling docs to be less confusing regarding the dd-trace-go v2 release.

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. Your branch name MUST follow the <slack_username>/<branch_name> convention, or your pull request will not pass in CI. If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/hannahkm/clarify-profiling-docs/profiler/enabling/go

[felixge]

Hm, I don't think this PR clarifies enough.

What we need is a link to a page that explains:

• What is v2?
• Where does it sit in the product lifecycle? (preview?)
• Should I use it for new projects?
• Should I migrate? (link to migration docs)
• What's are the major differences between v1 and v2, by product? (for profiler this means explicitly stating that there are no major changes)

IMO #25897 created a very confusing situation for customers, and it's not limited to profiling. So my comment applies to all of our mentions for v2.

So I would strongly encourage considering making a larger docs update for this.

Anyway, I made some inline comments that should help getting the profiling docs into a better shape in the meantime.

[felixge]

Why 1.x and 2.x? The old v1 or v2 comments were fine IMO.

[hannahkm]

I wanted to keep the comments consistent between here and the code on lines 51/52 so that the new instructions at the top would make more sense. I'm open to changing both to either v1/v2 or 1.x/2.x; what do you think?

[hannahkm]

@felixge Good points; thank you for the review! Agree that we could clarify some points throughout the docs. Let's fix the profiler page for now, and I'll open another PR to start addressing some other issues.

[brett0000FF]

@felixge - I made another iteration in 09f19bf. Let me know what you think. I thought we could further simplify this for users by focusing primarily on v2, especially since this page is for new users installing the profiler. Per @darccio , new users should use v2 moving forward (after GA).

Agree on your note about more context needed. I'll work to flesh out the migration page a bit more in Hannah's separate PR. But I think for the sake of simplicity, most users who come to this page shouldn't have to worry about v1 at all. They should be directed to the newest version that will continue receiving updates and features.

[brett0000FF]

@felixge - I also enhanced our migration guide to be a better source of information for our users in Hannah's separate PR. Preview (Note: Still needs review).

[hannahkm]

Closing in favor of using #28292