chore(deps): bump @opentelemetry/semantic-conventions to 1.28

[trivikr]

Which problem is this PR solving?

• https://github.com/open-telemetry/opentelemetry-js/releases/tag/semconv%2Fv1.28.0

Short description of the changes

• Updates @opentelemetry/semantic-conventions to 1.28

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (2f5d1de) to head (9f2acaf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2549   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files         169      169           
  Lines        8018     8018           
  Branches     1632     1632           
=======================================
  Hits         7277     7277           
  Misses        741      741           

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[trentm]

This should be discussed.
Over in open-telemetry/opentelemetry-js#5182 we are discussing the advice/recommendations/policy for using the "incubating" entry-point of the semconv JS package.

The rough concensus is that we will pin the semconv dep for a package when it is using the incubating entry-point, because in general there can be (hopefully rare) breaking changes in the incubating entry-point for a minor version release.

That's the reason this particular dep was pinned.

Currently the only packages in the contrib repo using the incubating endpoint are instrumentation-pg and intrumentation-aws-lambda. The latter isn't pinning the dep, mainly I assume because we are still working out how we want to handle the semconv dep.

[trivikr]

Pinned in 9f2acaf (#2549)

[trivikr]

Moving to draft. It can be rebased after #2569 is merged.