feat(semantic-conventions): update semantic conventions to v1.29.0

[trentm]

This also adds a changelog-gen.js script to help generate meaningful summary of changes in the semconv JS package.

Note: This change excludes the new 'network.interface.name' attribute because of open-telemetry/semantic-conventions#1777

---

Note: I did not update the weaver version to the latest. Doing so includes some whitespace fixes in the generated output that I wanted to do in a separate PR after this one.

[trentm]

In the last semconv update PR we discussed some generation of better changelogs for semconv updates. This PR adds a script to help with that. The result is in the diff of semantic-conventions/CHANGELOG.md
Here is a link to the rendered version of that:

https://github.com/trentm/opentelemetry-js/blob/tm-semconv-1.29.0/semantic-conventions/CHANGELOG.md#rocket-enhancement

• Be sure to open the "Full unstable changes" disclosure to see the detailed summary.
• Currently I setup the generated changelog to put unstable changes behind the disclosure, but stable changes, if any, would not be hidden behind a disclosure. It just so happens that v1.29.0 didn't include any stable changes.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.79%. Comparing base (d803022) to head (3463e5d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5356   +/-   ##
=======================================
  Coverage   94.79%   94.79%           
=======================================
  Files         310      310           
  Lines        7974     7974           
  Branches     1682     1682           
=======================================
  Hits         7559     7559           
  Misses        415      415           

[trentm]

A comment/suggestion on the changelog entry formatting from an OTel JS maintainers call earlier today: Separate disclosures for each change type. "Added" change type at the bottom.

[trentm]

Comment on changelog: separate disclosures for each category. "Added" at the bottom.

Here is a gist showing an example rendering. Note that I've manually faked some of the unstable changes as "stable" changes, so we can see some data in that section. (The actual 1.29.0 change did not include any changes to stable exports.)

https://gist.github.com/trentm/0decada22acd953813efb698a1985f29

In this rendering, both the stable and unstable sections are using the same <details> ... markup -- but the stable section defaults those disclosures being open (<details open> ...).

[JamieDanielson]

I love this! I suggested a change to the usage comments, and had a question around usage when the local version is passed into the changelog script, but it's not blocking since I don't see it being a common use case and happy to hear what I did wrong 😄

[JamieDanielson]

semconv export '${k}' was *un*-deprecated in this release!? Wassup?

😄

[trentm]

Merge queue checks failed in shim-opentracing tests for Node v20: https://github.com/open-telemetry/opentelemetry-js/actions/runs/13169707713/job/36757662560

   29 passing (37ms)
  1 failing

  1) OpenTracing Shim
       TracerShim
         starting spans
           translates span options correctly:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

+ 1738804269038.6545
- 1738804269038.6548
                   ^
      + expected - actual

      -1738804269038.6545
      +1738804269038.6548
      
      at Context.<anonymous> (test/Shim.test.ts:266:16)