Tracking issue: refactor `versioning` tests after the `write` operation is updated to return the version ID

[meteorgan]

Currently, the write operation does not return any metadata. As a result, in PR #5132, all versioning tests utilize the stat operation to retrieve the current object versions. Once the write operation is update to return the version ID, we can eliminate the need for these additional stat operations.

[Xuanwo]

Hi, I think this issue is part of a bigger scope that returning metadata after writing. This will require a major refactor of our write-related public API.

[meteorgan]

Hi, I think this issue is part of a bigger scope that returning metadata after writing. This will require a major refactor of our write-related public API.

Yes. as I mentioned in: https://github.com/apache/opendal/issues/2611#issuecomment-2363304110. I'll submit a RFC for this. This issue serves as a reminder to refactor the code in #5132.

[meteorgan]

I'm considering whether we really need this, as not all services can return a version. We still need to use stat in some scenarios. Checking the metadata returned from write could make the tests more complicated.

[Xuanwo]

Services that support versioning seem to allow retrieving the version after writing. I have checked S3, GCS, and Azblob. Not sure about other services.

[Xuanwo]

I'm considering whether we really need this, as not all services can return a version. We still need to use stat in some scenarios. Checking the metadata returned from write could make the tests more complicated.

Let's close this...