RaiseEvent-Call doesn't transmit content/body to Orchestrator

Hello,
I'm running a durable function with the human interaction pattern like in [the human interaction example](https://github.com/Azure/azure-functions-powershell-worker/blob/dev/examples/durable/DurableApp/HumanInteractionOrchestrator/run.ps1) . I successfully raise the event in a separat azure function via a HTTP call according to the [documentation](https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-external-events?tabs=powershell). In [line 22](https://github.com/Azure/azure-functions-powershell-worker/blob/df570c205232b9f3865520541ca032e9a5430d1a/examples/durable/DurableApp/HumanInteractionOrchestrator/run.ps1#L22), `$approvalEvent`, the return value of the `Start-DurableExternalEventListener` is used as the input for the activity. I assume that that's the value of the body that's send with the HTTP-call to raise the event, although it is not actually used in the activity itself in the example. I managed to capture the message in the queue, and the body is in there under `TaskMessage.Event.Input`. If I convert the `$approvalEvent` to JSON, it is just `"{}"`.
Is the message body not available in powershell or is there a cmdlet to query the data? The documentation is incomplete on this so far.

Please let me know if I can provide further information! Thank you!

Best regards,
Oliver

Start with examples/durable/DurableApp/HumanInteractionOrchestrator/run.ps1, especially line 22, and trace the value returned by Start-DurableExternalEventListener from the HTTP-raised event. Compare it with the queue's TaskMessage.Event.Input payload and determine how the request body should be exposed to PowerShell; done means the event content is available to the listener or its documented usage is corrected.

Written by the indexing model from the issue text.