Added async settle methods in ServiceBusReceivedMessageContext as an alternative to the blocking calls

[ahayanm001]

Description

ServiceBusReceivedMessageContext (used by ServiceBusProcessorClient) uses blocking .block() calls for message settlement which is not ideal in a reactive stack. From the outside the processor seems to support asynchronous handling (using the async client), but internally the settlements methods call .block(), as mentioned, which turns async processing into blocking I/O. In our case (Kotlin coroutine-based environment), this blocks the entire thread in the dispatcher.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

Thank you for your contribution @ahayanm001! We will review the pull request and get back to you soon.

[ahayanm001]

@microsoft-github-policy-service agree