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?

Comienza comparando el contexto que se pasa a main() para los bindings con el contexto disponible dentro de las orquestaciones de Durable Functions. Comprueba cómo se exponen trace_context y operation_Id en cada ruta y, a continuación, confirma que una orquestación puede acceder al contexto clásico de Azure Function o a un valor equivalente para rastrear las entradas de dependencias con la misma operation_Id.

Escrito por el modelo de indexación a partir del texto del issue.