404 Pull Error when trying to update Metadata when replication is disabled in S3 storage

#### Describe the bug
After uploaded a file when I go to add or edit the metadata it give a 404 Not Found error.
It works when adding metadata on initial upload of a file but not when we try to update.

#### To Reproduce

Steps to reproduce the behavior:

1. Open console
2. Upload a file
3. Attempt to add metadata
4. Scroll down to '....'
5. See error

#### Expected behavior
We should be able to update and add metadata to a file.

#### Screenshots

#### Desktop (please complete the following information):

- OS: Windows 11
- Browser Edge/Chrome
- Version 139.0.3405.102

#### Additional context
- We have Metadata/Replication turned off on our S3 but it works in our older build of BCBox
- Network Response:
{
"type": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"title": "Not Found",
"status": 404,
"detail": {
"name": "NoSuchVersion",
"$fault": "client",
"$metadata": {
"httpStatusCode": 404,
"requestId": "8e22ee13:19793ac813f:d3276:3fab",
"extendedRequestId": "d1c9d35c53a240bc73339d52e234f24714121b7eb7f72841eee1746c56ce784e",
"attempts": 1,
"totalRetryDelay": 0
},
"Code": "NoSuchVersion",
"Resource": "data-bcstats-lockbox-dev-bkt/dev5/PXL_20250504_212028686.jpg",
"RequestId": "8e22ee13:19793ac813f:d3276:3fab",
"message": "Indicates that the version ID specified in the request does not match an existing version."
}
}

Reproduce the issue through the console by uploading a file, then attempting to add or edit metadata with S3 replication and metadata disabled. Start by tracing the upload and metadata-update flows and inspect the 404 NoSuchVersion response. Done means metadata can be added or updated successfully in this configuration without a 404.

Written by the indexing model from the issue text.