feat(tracing): Send sentry.segment.name.source instead of sentry.span.source attribute

[Lms24]

Following the deprecation of sentry.span.source, this PR renames the attribute from sentry.span.source to sentry.segment.name.source.

Background: We currently decided not do do segment name clustering for streamed spans but should we ever choose to do it, sentry.segment.name.source will be the attribute carrying the name source for it. Either way, sentry.span.source has no effect anymore.

Reviewers, please let me know about your preferences:

• Technically, the renaming might break user callbacks relying on the old attribute. Since this only affects streamed spans I think it's fine but if you have other policies for span first, we can also double-write.
• I decided to rename SegmentSource to SegmentNameSource for consistency. Is this considered breaking? If so, happy to revert as it's purely a cosmetic change IMHO.

[github-actions]

Codecov Results 📊

✅ 91854 passed | ⏭️ 6302 skipped | Total: 98156 | Pass Rate: 93.58% | Execution Time: 315m 53s

📊 Comparison with Base Branch

Metric	Change
Total Tests	—
Passed Tests	—
Failed Tests	—
Skipped Tests	—

✨ No test changes detected

All tests are passing successfully.

✅ Patch coverage is 100.00%. Project has 2478 uncovered lines.
✅ Project coverage is 89.68%. Comparing base (base) to head (head).

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    89.68%    89.68%        —%
==========================================
  Files          193       193         —
  Lines        24004     24004         —
  Branches      8340      8340         —
==========================================
+ Hits         21526     21526         —
- Misses        2478      2478         —
- Partials      1387      1387         —

---

Generated by Codecov Action

[Lms24]

Seer pointed out that the "wrong" enum was used here (no big deal as the values were identical). So I changed it over to SegmentNameSource

[ericapisani]

Still need to take a look at the changes themselves but to initially answer your questions in the pull request summary:

Technically, the renaming might break user callbacks relying on the old attribute. Since this only affects streamed spans I think it's fine but if you have other policies for span first, we can also double-write.

As of right now I don't believe there are callbacks relying on this attribute so I think this should be a safe to do right now.

I decided to rename SegmentSource to SegmentNameSource for consistency. Is this considered breaking? If so, happy to revert as it's purely a cosmetic change IMHO.

Since the underlying value hasn't changed, this isn't considered this breaking. 🚀

[ericapisani]

🚀