[@azure/functions-extensions-servicebus] Message settlement increases the latency of individual invocations compared to autocomplete

The gRPC calls to settle messages increases the latency of individual invocations (20ms+). This is much less performant for a high throughput function and means that we are less likely to adopt the SDK. Would the recommendation be to use autocomplete on high throughput functions and only utilise the methods for deadlettering and abandoning?.

Additionally the type seems to be incorrect for service bus topic triggers, where the sdkBinding property is not present on the ` ServiceBusTopicFunctionOptions` type.

Locate the Service Bus settlement gRPC calls and the ServiceBusTopicFunctionOptions type definition. Compare individual-invocation latency for settlement and autocomplete in a high-throughput function, then verify the topic-trigger type against the runtime binding shape. Done means the latency trade-off is measured and the missing sdkBinding type behavior is resolved or clearly documented.

Written by the indexing model from the issue text.