[State CosmosDB] Preserve property order

[RobertConanMcMillan]

When reading an entry from a CosmosDB backed state store, properties are returned in seemingly random order, often shuffled differently on each fetch.

This breaks System.Text.Json polymorphism, as the $type (or other delimiter) must be the first property read in an object.

Expected Behavior

The JSON should not be modified or altered, when read from the state store.

When the value:

{
    "$type": "some-type",
    "value": "some-value"
}

Is stored in the state store, get state should return:

{
    "$type": "some-type",
    "value": "some-value"
}

Actual Behavior

When the value:

{
    "$type": "some-type",
    "value": "some-value"
}

Is stored in the state store, get state will randomly return either:

{
    "$type": "some-type",
    "value": "some-value"
}

or

{
    "value": "some-value"
    "$type": "some-type"
}

Steps to Reproduce the Problem

1. Store JSON value in state.azure.cosmosdb state store
2. Read value from state store
3. Compare JSON property order

Release Note

RELEASE NOTE: FIX CosmosDB state returns shuffled JSON

[berndverst]

The Dapr API does not make any guarantees about the ordering of fields. This is not part of our API contract @RobertConanMcMillan. Therefore I do not see this as a bug.

However, I'm happy to accept PRs.