Azure SQL Server state store changes order of transaction

[shubham1172]

Similar to #1209

Expected Behavior

For the following transaction:

upsert key1 value1
delete key1
upsert key2 value2

Expectation is that key1 should be deleted, key2 should have a value of value2.

Actual Behavior

key1:value1 is present, along with key2: value2.

Steps to Reproduce the Problem

Please use the JS snippet from the referenced issue (1209)

Details

In the transaction snippet for this state store, the delete operations are always executed before upsert operations. This results in failure with message delete affected only 0 rows, expected 1 whenever the above tx is attempted.

Release Note

RELEASE NOTE: FIX Azure SQL Server state store's transaction API to respect order of operations.

[shubham1172]

/assign