ocis: Broken tests in drop zone in reva master

in https://github.com/cs3org/reva/pull/3469, to not override files having the same names in a drop zone, we are appending an uuid at the end of a file name. This is unfortunately breaking some acceptance tests, like for example this scenario (from https://drone.cernbox.cern.ch/cs3org/reva/9673/10/6):

  Scenario: Uploading same file to a public upload-only share multiple times via new API
    # The new API does the autorename automatically in upload-only folders
    Given user "Alice" has created a public link share with settings
      | path        | FOLDER |
      | permissions | create |
    When the public uploads file "test.txt" with content "test" using the new public WebDAV API
    And the public uploads file "test.txt" with content "test2" using the new public WebDAV API
    Then the HTTP status code of responses on all endpoints should be "201"
    And the following headers should match these regular expressions
      | ETag | /^"[a-f0-9:\.]{1,32}"$/ |
    And the content of file "/FOLDER/test.txt" for user "Alice" should be "test"
    And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2"

Now, this test is supposed to check for a file containing a number (2), that didn’t override the original file. But even testing in https://ocis.owncloud.com this does not happen, and the original file is overwritten. So which is the expected behavior in OCIS? We would like than to modify the test for reva master to pass the PR @phil-davis