Retrieve Parent Context of a Flow on Error

We have a shared pipeline with a hierarchy of nested flows. When an error occurs in a deeply nested flow, our support team needs to determine its execution context (parent flow, grandparent flow, etc.) for efficient troubleshooting.

I propose the following solutions but am open to alternative implementations from ETLWorks:
- Option 1: Retrieve the entire hierarchy at the start of the pipeline and store it as a reference. When an error occurs, use the failing flow's name to look up its position in the stored hierarchy and determine its parent-child relationships. The execution context can then be formatted as a string variable and sent to an observability tool.
- Option 2: Provide a function that dynamically returns the current execution context, including parent flows, as a string.

This feature would significantly improve debugging. This request follows up on support request #9799. Please let me know if more details are needed.