Catch 404 from BlobStore during Versions Purge

Repro of the issue: Delete API calls for /record//versions fails with a 404 and "The specified blob does not exist" due to Cosmos Metadata and Blob Storage Inconsistency.

Created three versions of a storage record:

"gcsVersionPaths": [
        "osdu:wks:reference-data--ProcessingParameterType:1.0.0/opendes:reference-data--ProcessingParameterType:568f7b7f96c24c8bb7d2d2cbc2d303e3/1738020064521286",
        "osdu:wks:reference-data--ProcessingParameterType:1.0.0/opendes:reference-data--ProcessingParameterType:568f7b7f96c24c8bb7d2d2cbc2d303e3/1738020448629865",
        "osdu:wks:reference-data--ProcessingParameterType:1.0.0/opendes:reference-data--ProcessingParameterType:568f7b7f96c24c8bb7d2d2cbc2d303e3/1738020453636681"
  ],

Deleted one of them 1738020064521286 manually from blob store, so only two of them exist now.

Calling purgeVersions fails with 404.

Fix:

Eating 404s from blob to continue deleting other available versions. Sample logs from catching the exception: