fix(ray): long running spans have now the right resource name [backport 3.16] (#14904)

Backport 109a976 from #14818 to 3.16.

Long running spans were appearing with the operation name as the span
name making the trace hard to interpret until the job finished.

This PR adds the resource name to partial flush of long running spans

Co-authored-by: Louis Tricot <[email protected]>

Author: dd-octo-sts[bot]

ddtrace/contrib/internal/ray/span_manager.py

@@ -159,6 +159,7 @@ def _create_resubmit_timer(self, submission_id: str, time: float) -> None:
     def _recreate_job_span(self, job_span: Span) -> Span:
         new_span = Span(
             name=job_span.name,
+            resource=job_span.resource,
             service=job_span.service,
             span_type=job_span.span_type,
             trace_id=job_span.trace_id,

releasenotes/notes/fix-ray-ressource-name-d97bda5a3e62eabe.yaml

@@ -0,0 +1,4 @@
+---
+fixes:
+  - |
+    ray: This fix resolves an issue where long-running spans did not preserve the correct resource name when being recreated.