chore(deps): update Go OTel SDK

[lizthegrey]

Which problem is this PR solving?

• Review found a bug in addOverCapAttrs()

Short description of the changes

• Import fixes from upstream sdk/trace: use slices.Grow() to avoid excessive runtime.growslice() open-telemetry/opentelemetry-go#4818

[MikeGoldsmith]

I like the work you've done in the upstream OTel SDK but I think we should wait for it to merge before we use it here. It may change further or even be rejected and we'd diverge from the SDK.

[lizthegrey]

I like the work you've done in the upstream OTel SDK but I think we should wait for it to merge before we use it here. It may change further or even be rejected and we'd diverge from the SDK.

Unfortunately, this is necessary for my load testing as without the fix I'm unable to generate enough load to saturate refinery.

[MikeGoldsmith]

How are you conducting the tests? I think building or running the loadgen from this branch should be okay to run tests with the fix, it just means merging main back into this branch to make sure it has everything.

I'm only reluctant because until it merges, we'll need to open new PRs for each subsequent commit and we all know some PRs can take some tweaking and lobbying to get merged in OTel.

[lizthegrey]

How are you conducting the tests? I think building or running the loadgen from this branch should be okay to run tests with the fix, it just means merging main back into this branch to make sure it has everything.

I'm only reluctant because until it merges, we'll need to open new PRs for each subsequent commit and we all know some PRs can take some tweaking and lobbying to get merged in OTel.

A maintainer has taken responsibility for it to the point of filing an issue for go1.20 cleanup after it is merged :) should get merged in the next day or so, and in the meanwhile this is not a public repo, and is in use nowhere else in Honeycomb yet besides my test.

open-telemetry/opentelemetry-go#4819

[MikeGoldsmith]

After discussing with @lizthegrey and seeing the upstream PR starting to get approvals, we agreed it's okay to merge this PR now and then fix it up once the next otel-go SDK is released.

[lizthegrey]

Used a cherry-pick on top of v1.21.0 in case there are any problems lurking in otel-go at main.