fix: bug on tracing where components are in a loop in a pipeline (#8576)

* Fix to tracing parent spans on loops

* Fix linting

* Add release notes

---------

Co-authored-by: Silvano Cerza <silvanocerza@gmail.com>

haystack/core/pipeline/pipeline.py

@@ -98,7 +98,9 @@ def _run_subgraph(  # noqa: PLR0915
         cycle: List[str],
         component_name: str,
         components_inputs: Dict[str, Dict[str, Any]],
+        *,
         include_outputs_from: Optional[Set[str]] = None,
+        parent_span: Optional[tracing.Span] = None,
     ) -> Tuple[Dict[str, Any], Dict[str, Any]]:
         """
         Runs a `cycle` in the Pipeline starting from `component_name`.
@@ -162,7 +164,7 @@ def _run_subgraph(  # noqa: PLR0915
                     msg = f"Maximum run count {self._max_runs_per_component} reached for component '{name}'"
                     raise PipelineMaxComponentRuns(msg)
 
-                res: Dict[str, Any] = self._run_component(name, components_inputs[name])
+                res: Dict[str, Any] = self._run_component(name, components_inputs[name], parent_span=parent_span)
 
                 # Delete the inputs that were consumed by the Component and are not received from
                 # the user or from Components that are part of this cycle
@@ -439,7 +441,7 @@ def run(  # noqa: PLR0915, PLR0912
                     # are run doesn't make a different whether we pick the first or any of the others a
                     # Component is part of.
                     subgraph_output, subgraph_extra_output = self._run_subgraph(
-                        cycles[0], name, components_inputs, include_outputs_from
+                        cycles[0], name, components_inputs, include_outputs_from=include_outputs_from, parent_span=span
                     )
 
                     # After a cycle is run the previous run_queue can't be correct anymore cause it's

releasenotes/notes/fix-tracing-bug-on-looping-components-in-pipeline-81812f72956b24ef.yaml

@@ -0,0 +1,4 @@
+---
+fixes:
+  - |
+    Fix tracing `Pipeline` with cycles to correctly track components execution