API/Acceptance tests for Async Upload

[patrickjahns]

With #32414 merged, we are looking to have simple API acceptance tests, that generally test this behavior.

Once these are working, we should consider also using these test steps for:

• objectstore / files_primary_s3 tests are now in core, so they all run with S3 in nightly builds
• firewall - issue https://github.com/owncloud/firewall/issues/536 - PR https://github.com/owncloud/firewall/pull/540
• antivirus - issue: API/Acceptance tests for Async Upload files_antivirus#274 - PR check upload when using async move files_antivirus#276

Double checking for

• guests - issue API/Acceptance tests for Async Upload guests#278 - PR more chunking upload tests guests#280
• workflow (manually tested)

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @phil-davis.

Possibly related issues are #22492 (test), #31579 (test), #22485 (test), #30493 (Rename integration API tests to acceptance), and #32559 (acceptance tests - stop uploading when receiving an error).

[individual-it]

@DeepDiver1975 @PVince81 in the case of an error e.g. MOVE a file that does not exist, the async operation still replies with an 202 code. There is a correct error code in OC-JobStatus-Location, but the request itself returns 202. Is that correct?

[PVince81]

I think I'd rather expect a 404 and have an existence check happen before the job goes async.

[individual-it]

@PVince81 issue opened here #32598

[individual-it]

other interesting tests:

• file_versioning PR Test file_versions with chunking upload #33743
• files_classifier https://github.com/owncloud/files_classifier/pull/120

[individual-it]

moving to next sprint for the rest of the work

[individual-it]

all done, closing