Ability to access 'classic' Azure Function Context, so that I can trace against the same operation_Id

💡 **Feature description**
Currently, I associate my opentelemetry 'dependency' log entries against their parent operation_Id by running the following:
``` python
carrier = {
"traceparent": azf_context.trace_context.Traceparent,
"tracestate": azf_context.trace_context.Tracestate,
}
context = extract(carrier)
```

(as per azure's own docs)

The azure function context is passed in as the final parameter when main() is called by any binding.

While this seems to work for activities, I am unable to find a similar context information from within durable function orchestrations.

Can you help me find out what I'm missing -- or add it?

Start by comparing the context passed to main() for bindings with the context available inside durable function orchestrations. Check how trace_context and operation_Id are exposed in each path, then confirm that an orchestration can access the classic Azure Function context or an equivalent value for tracing dependency entries against the same operation_Id.

Written by the indexing model from the issue text.