Generating histogram boundaries from weaver.yaml

[itssaharsh]

Adding support for histogram boundaries to be generated from weaver

fixes #8002

[dashpole]

I think the latest is the v1.40.0 semconv. @MrAlias do we usually just update the latest version of semconv, or should we wait for the next semconv version release? Or should we update more than one version?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.6%. Comparing base (a3941ff) to head (55a119c).
⚠️ Report is 23 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #8015   +/-   ##
=====================================
  Coverage   81.6%   81.6%           
=====================================
  Files        304     304           
  Lines      23424   23424           
=====================================
+ Hits       19130   19131    +1     
  Misses      3906    3906           
+ Partials     388     387    -1     

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[MrAlias]

I think the latest is the v1.40.0 semconv.

Correct 👍

@MrAlias do we usually just update the latest version of semconv, or should we wait for the next semconv version release? Or should we update more than one version?

We update the latest if the changes are backwards compatible. Otherwise, we wait for the next release to apply the change.

Any published stable package needs to remain backward compatible. New packages can include changes to the API.

[MrAlias]

This looks technically backwards compatible. But we should probably just wait until v1.41.0 to prevent confusion for users already using v1.40.0.

[itssaharsh]

should I convert this to draft and reopen after the semconv release?