Azure Service Bus output binding for Azure Functions is limited to message body

The way the [service bus output bindings are implement](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-output?tabs=in-process%2Cextensionv5&pivots=programming-language-javascript) seem to only support the message body... You can't set messageId, sessionId, applicationProperties, etc. This makes it useless almost any real world use cases.

Are there plans to properly implement this binding?

Found these related "User Voice" issues, but they are stale and have no comments addressing this issue:

https://feedback.azure.com/d365community/idea/eea36d62-f224-ec11-b6e6-000d3a4f0da0
https://feedback.azure.com/d365community/idea/df849c4f-f224-ec11-b6e6-000d3a4f0da0

Start with the linked Azure Functions Service Bus output-binding documentation and compare the documented behavior with the current .NET worker implementation. Identify the binding entry points and tests, then determine the expected handling of messageId, sessionId, and applicationProperties before defining what complete support would require.

Written by the indexing model from the issue text.