[osdu env only] /versions/{version_id} Failed to process JSON - Unexpected character

**FLAKY ISSUE **

STEPS:

1. Create any record
2. Get version
3. Use /versions/{version_id} endpoint and request not full version of the record Example: https://osdu-glab.msft-osdu-test.org/api/rafs-ddms/v1/samplesanalysesreport/opendes:work-product-component--SamplesAnalysesReport:Test/versions/168692958932901

1686929589329011 - is a full version of the record

NOTE: Since the case is FLAKY, it is better to try to execute the query by removing one digit from the version in order to catch the error

More often reproduced in autotest: test_get_non_existent_version_of_the_record

AR: {

"code": 400,
"reason": "Failed to process JSON.",
"message": "Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')_ at [Source: (byte[])\"�<?xml version=\"1.0\" encoding=\"utf-8\"?><EnumerationResults ServiceEndpoint=\"https://osdumvpdp1glabky7vdata.blob.core.windows.net/\" ContainerName=\"opendes\"><Prefix>exxonmobil:rafsddms:work-product-component--SamplesAnalysesReport:1.0.0/opendes:work-product-component--SamplesAnalysesReport:Test/168692958932901</Prefix><Blobs><Blob><Name>exxonmobil:rafsddms:work-product-component--SamplesAnalysesReport:1.0.0/opendes:work-product-component--SamplesAnalysesReport:Test/1686929589329011</Name><Proper\"[truncated 680 bytes]; line: 1, column: 5]"

}

ER: {

"code": 404,
"reason": "Version not found",
"message": "The version '168692958932901' can't be found for record opendes:work-product-component--SamplesAnalysesReport:Test"

}