feat(repository): Use cosmos patch operations and fix response detail

[cap-ang]

List of Changes

• Update README
• Update Status end-time via CosmosPatchOperation https://learn.microsoft.com/en-us/azure/cosmos-db/partial-document-update
• Update Logging
• Update detail with static mapping (the problem was a many responses poorly aggregated because the detail differs by a few characters even if it is of the same type)
• General Refactoring

Motivation and Context

• The PR wants fix poorly aggregated responses and use CosmosPatchOperation when possible

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[FedericoRuzzier]

LGTM 👍

[FedericoRuzzier]

Fix sonar then good to go

[github-actions]

This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[sonarqubecloud]

Quality Gate failed

Failed conditions
77.6% Coverage on New Code (required ≥ 80%)
D Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint