Cosmos DB: Mutations should be done in the same transaction as other mutations in the same request

### What happened?

Multiple mutations should be part of the same transaction (assuming the items are in the same container and logical partition). That way they can be rolled back in an atomic way. It also ensures that no unexpected data is returned in the result of a mutation in case of concurrent updates.

### Version

0.7.6

### What database are you using?

CosmosDB NoSQL

### What hosting model are you using?

Static Web Apps (SWA)

### Which API approach are you accessing DAB through?

GraphQL

### Relevant log output

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct