[Feature] DynamoDB Transactional Storage Provider

[scalalang2]

Microsoft Reviewers: Open in CodeFlow

Background

Currently users can use distributed transaction in DynamoDB by using StateStorageBridge, but it aggregates all pending state into a single entry, Since DynamoDB limits the size of each entry upto 400 KB. It's not applicable for larger transactions. the data must be split into multiple entires, similar to the method used with Orleans.Transactions.AzureStorage

resolve #9150

[scalalang2]

We are a team working on an unreleased project from one of South Korea's largest game development companies.
This provider has functioned properly during both internal testing and a pre-release test on Steam.

I'd appreciate that if the core team could review the code.

[scalalang2]

I noticed that the transaction in DynamoDB is quite slow compared to individual DeleteItem, PutItem and UpdateItem.
Can I replace the the transactional operation to individual calls? @ReubenBond

The comment here describes that it doesn't need to operate atomically.

assemble all storage operations into a single batch
these operations must commit in sequence, but not necessarily atomically
so we can split this up if needed