Cosmos DB: Adds Patch Support

[sourabh1007]

Why make this change?

Today, in cosmos DB, we have ability to update the item which is actually replace the item. Adding new operation i.e. patch where customer would have ability to "patch" an item.
PATCH would be available only for Cosmos DB.

What is this change?

Before going further, it is highly recommended to go through below docs:

1. How patch works in Cosmos DB https://learn.microsoft.com/en-us/azure/cosmos-db/partial-document-update#supported-operations
2. Limitations: https://learn.microsoft.com/en-us/azure/cosmos-db/partial-document-update#supported-modes
3. How it works with SDK: https://learn.microsoft.com/en-us/azure/cosmos-db/partial-document-update-getting-started?tabs=dotnet#prerequisites

To Summarize, here is a simple example of patch:

List<PatchOperation> operations = new ()
{
    PatchOperation.Add("/color", "silver"),
    PatchOperation.Remove("/used"),
    PatchOperation.Increment("/price", 50.00),
    PatchOperation.Add("/tags/-", "featured-bikes")
};

ItemResponse<Product> response = await container.PatchItemAsync<Product>(
    id: "e379aea5-63f5-4623-9a9b-4cd9b33b91d5",
    partitionKey: new PartitionKey("road-bikes"),
    patchOperations: operations
);

You need to generate PatchOpertation which need below information:
a) Operation type i.e. Set, Add, Remove etc
b) Attribute Path where operation needs to be applied i.e "/color", "/used" in above example
c) New value

What DAB supports?

1. We decided to support only Set operation, as it solves the purpose to update an item. It means, you cannot perform any specific operations like remove, move etc.
2. There is no special handling for an array.
3. If the target path specifies an element that doesn't exist, it's added.
4. If the target path specifies an element that already exists, its value is replaced.

Changes as part of this PR:

1. Generate patch operation for given entities
   
2. Generate PatchPlanetInput without id field as using patch operation you can not update an Id
   
3. Implement patch operation
   a) It translates the passed item into "patchoperation" by traversing the item.
   b) Checks if number of patch operations are less than 10 or more than 10 (as cosmsodb supports at max 10 patch operations at a time)
   c) If it is less than or equal to 10, it fires patch call with patch operations
   d) If it is greater than 10, then it creates a transaction batch of patch call, with 10 patch operations in each patch call. (RU exhaustive but functionally it works)

Pictorial Overview of the implementation

flowchart TD
    User[fa:fa-user User]-->| patch operation |DAB
    subgraph DAB[DAB]
        Authorization[Authorization]-->Patch
        subgraph Patch[Patch Operation]
        PatchOperation[Generate Patch 'Set' Operations with passed item] -->CheckCount{Number of Patch Operation > 10}
        CheckCount --> |No| SDKOperation[SDK Patch call]
        CheckCount --> |Yes| TransactionBatch[Create a batch of patch calls with max 10 patch operations ]-->SDKBatchOperation[SDK ExecuteBatch call]
        end
    end

Authorization for this new Mutation Operation:
update access would be applied for patch and update operations both.

How was this tested?

• Integration Tests
• Unit Tests

Sample Request(s)

Refer test cases.

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[Aniruddh25]

Waiting on clarification on the need to introduce a patch permission..

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[Aniruddh25]

previous comments have been addressed, but I need more time to look at few other files.. so reset my review. If this gets approved before that, feel free to merge it in.

Already addressed..

[sourabh1007]

/azp run

[sourabh1007]

/azp run

[neeraj-sharma2592]

LGTM

[sourabh1007]

/azp run