MySQL 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

Both key1:value1 and key2:value2 are present.

Steps to Reproduce the Problem

Please use the JS snipped from the reference issue (1209)

Details

Under the hood, MySQL store attempts all the deletions first, followed by all the upserts. This changes the actual ordering of operations within the transaction, giving wrong results.

Release Note

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

[shubham1172]

/assign