Update go code excerpts

[svrnm]

Replaces #4678

[chalin]

Is this just a run of the code-excerpt tooling over the docs?
What's left to do (why the draft status)?

[svrnm]

Is this just a run of the code-excerpt tooling over the docs? What's left to do (why the draft status)?

If I remember correctly a file was extracted (lines 411 to 423) and this needs to be added to the text. Tbh I forgot about this issue/didn't get to it

[pellared]

FYI the changes look wrong. See https://github.com/open-telemetry/opentelemetry-go/blob/main/example/dice/rolldice.go

[svrnm]

FYI the changes look wrong. See open-telemetry/opentelemetry-go@main/example/dice/rolldice.go

the changes are based on the release we have pinned the submodule to (v1.27.0), we might need a more robust workflow here, especially when files are forked out

[pellared]

the changes are based on the release we have pinned the submodule to (v1.27.0),

And we already have v1.28.0:

• https://github.com/open-telemetry/opentelemetry-go/blob/v1.28.0/example/dice/rolldice.go

[svrnm]

the changes are based on the release we have pinned the submodule to (v1.27.0),

And we already have v1.28.0:

* [open-telemetry/opentelemetry-go@`v1.28.0`/example/dice/rolldice.go](https://github.com/open-telemetry/opentelemetry-go/blob/v1.28.0/example/dice/rolldice.go?rgh-link-date=2024-07-25T10%3A36%3A57Z)

That's what I mean with we need a robust workflow... we might want to consider creating automation for bumping the submodules whenever an update occurs, however if these files get changed but no new version is released, we still need to go down the manual path.

[svrnm]

I need to take a fresh look at this