Go: Roll the dice

[pellared]

Towards #2623
Towards open-telemetry/opentelemetry-go#4531

Rewrite of: https://opentelemetry.io/docs/instrumentation/go/getting-started/
Preview: https://deploy-preview-3310--opentelemetry.netlify.app/docs/instrumentation/go/getting-started/

Based on open-telemetry/opentelemetry-go#4539

[pellared]

@pellared should this go in after the Go PR is merged, or can we consider this orthogonally?

@cartermp, please consider this orthogonally

1. I will make further PR(s) if there would be any changes done in Add dice example opentelemetry-go#4539. I did the same for manual metrics docs Go: Refine Initialize Metrics #3305
2. I plan to improve other Go docs pages. I want to have this one merged first to reduce the number of open PRs. I prefer going baby steps.

[cartermp]

Overall this looks great. I think it'd be helpful to have an ending section called Next Steps, like the python docs here: https://deploy-preview-3310--opentelemetry.netlify.app/docs/instrumentation/python/getting-started/#next-steps

Doesn't have to be copied verbatim -- I think mainly we should link to the manual instrumentation page and the exporters page.

[cartermp]

Suggested change

	You will learn how you can instrument a simple application automatically, in
	such a way that [traces][] and [metrics][] are emitted to the console.
	You will learn how you can instrument a simple application using
	instrumentation libraries and custom instrumentation with
	OpenTelemetry APIs. You'll create [traces][] and [metrics][] and emit
	them to the console.

[cartermp]

Bigger suggestion here -- since we're not using the go autoinstrumentation agent (maybe that comes in the future!) I think it's worth rephrasing here to emphasize libraries and custom instrumentation with APIs.

[pellared]

Should I also mention the SDK? Isn't the term "OpenTelemetry APIs confusing, because there is also OpenTelemetry API which is used for custom instrumentation?

I will simply change to

Suggested change

	You will learn how you can instrument a simple application automatically, in
	such a way that [traces][] and [metrics][] are emitted to the console.
	You will learn how you can instrument a simple application manually, in
	such a way that [traces][] and [metrics][] are emitted to the console.

But I am open for further suggestions.

PS. I have created #3308 before this PR and I have forgotten to remove "automatically" 🤦

[pellared]

9b0888d

[pellared]

Overall this looks great. I think it'd be helpful to have an ending section called Next Steps, like the python docs here: https://deploy-preview-3310--opentelemetry.netlify.app/docs/instrumentation/python/getting-started/#next-steps

Fine. I will add it. See 4c82660 🤣

[dashpole]

lgtm overall

[pellared]

@cartermp I think it is good to merge.