fix: Save lock-token from receive_deferred_messages AMQP payload, into ServiceBusReceivedMessage

[ashleysommer]

Description

Save lock-token from receive_deferred_messages AMQP payload, so it can be used as the message's lock_token property. This allows the deferred message to be correctly renewed or settled (abandoned, completed, deferred again).

Fixes #42454

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.

Testing Guidelines

• Pull request includes test coverage for the included changes.

---

This is for initial review. I have not included anything in Changelog.
There are no tests at all in the codebase for deferred messages or anything to do with parsing deferred messages, so I don't know where to add a regression test for this.

[github-actions]

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

[ashleysommer]

@microsoft-github-policy-service agree

[Copilot]

Pull Request Overview

This PR fixes a bug where deferred Service Bus messages were not properly retaining their lock tokens from the AMQP payload, preventing proper message renewal and settlement operations. The fix ensures that when receiving deferred messages, the lock token from the AMQP response is correctly extracted and assigned to the ServiceBusReceivedMessage object.

Key changes:

• Extract lock token from AMQP payload for deferred messages in both transport implementations
• Store the received lock token in the message object during initialization
• Update the lock_token property to prioritize the received lock token over the delivery tag

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
_uamqp_transport.py	Extract lock token from deferred message AMQP payload and pass to message constructor
_pyamqp_transport.py	Extract lock token from deferred message AMQP payload and pass to message constructor
message.py	Store received lock token and prioritize it in the lock_token property

[github-actions]

Hi @ashleysommer. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[ashleysommer]

Yes, this PR is still needed, still waiting for a human to review it.

[ashleysommer]

This still needs human review, and needs someone to complete the final parts of adding regression tests and writing changelog.