Update docs to point to new semconv artifact

[jack-berg]

No description provided.

[jack-berg]

Would be great if we could have this version automatically update when new releases are published. Any tips from the maintainers on how to extend the auto-update-versions.yml github workflow with a new version? Is extending it as simple as it looks?

[cartermp]

@jack-berg yeah, it should be pretty simple to update. I think the main concern is further changes that require code updates? One of the reasons why we have the existing ones auto-update is because the large majority of the time it's just the version number that has to update. If that's the case for semconv artifacts for Java, then I'd be in favor of automating it.

[jack-berg]

@cartermp code changes are possible since the artifact is still alpha, but this was previously the case as well. For the most part, each release will be just a version bump. I'll make sure to followup in the rare event that a version bump coincides with a code change.

[cartermp]

Sounds good @jack-berg -- looks like a PR I merged introduced a merge conflict. Once that's done and you can update the refcache with npm run-and-fix then this should be good to go.