Fix transaction API for Azure Cosmos DB

[shubham1172]

Signed-off-by: Shubham Sharma [email protected]

Description

Similar to #1516, this introduces a logic to fix the ordering in a transaction. For a given key, only the latest operation is executed. The other operations are ignored. (From related PR: ) This is similar to what was proposed in #1209 (comment). For example, say the original transaction is:

upsert k1 v1  # redundant, gets deleted later
delete k1
delete k2     # redundant, gets set to v2 later
upsert k2 v2

Issue reference

Please reference the issue this PR will close: #1209

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• (NA) Created/updated tests, will be fixed with New conf test scenario for state stores: transaction order #1210
• (NA) Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[shubham1172]

Test from #1496

On master:

[codecov]

Codecov Report

Merging #1518 (86e1401) into master (0f44be4) will decrease coverage by 0.00%.
The diff coverage is 21.05%.

@@            Coverage Diff             @@
##           master    #1518      +/-   ##
==========================================
- Coverage   35.40%   35.40%   -0.01%     
==========================================
  Files         160      160              
  Lines       14616    14618       +2     
==========================================
  Hits         5175     5175              
- Misses       8888     8890       +2     
  Partials      553      553              

Impacted Files	Coverage Δ
bindings/alicloud/nacos/settings.go	33.33% <ø> (ø)
state/azure/cosmosdb/cosmosdb.go	13.71% <0.00%> (-0.21%)	⬇️
bindings/alicloud/nacos/nacos.go	35.60% <100.00%> (+0.36%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f1209fb...86e1401. Read the comment docs.

[shubham1172]

Ran the actors e2e test - actor_features, that covers state change scenarios, with changes from this PR.