Invoking Service Bus function via admin endpoint and passing payload + headers

The documentation [shows](https://learn.microsoft.com/en-us/azure/azure-functions/functions-run-local?tabs=windows%2Cisolated-process%2Cnode-v4%2Cpython-v2%2Cnon-http-trigger%2Ccontainer-apps&pivots=programming-language-csharp#tabpanel_6_non-http-trigger:~:text=There%20are%20two%20ways%20to%20execute%20non%2DHTTP%20triggers%20locally.) how to invoke HTTP-triggered functions. It shows Azure Storage Queues for non-HTTP functions, but that scenario is straightforward because the data posted is transformed into the Storage Queue payload as-is. With ASB, custom headers (application properties) can also be passed in addition to the message payload. Is it possible to achieve passing headers + body for the message? And if 'yes', what's the correct syntax?

Original question from [StackOverflow](https://stackoverflow.com/questions/79185784/run-local-azure-function-with-nservice-bus-service-bus-trigger).

Start with the linked Azure Functions local-invocation documentation and the admin endpoint for non-HTTP triggers. Check the Service Bus trigger behavior for message bodies and application properties, then document the supported request syntax and an example if both can be passed; done means the documentation answers the question unambiguously.

Written by the indexing model from the issue text.