async operation always returns HTTP code 202

[individual-it]

Steps to reproduce

1. try to MOVE a file that does not exist using the async operation
2. check the HTTP status code

Expected behaviour

4xx code should be returned see #32580 (comment)

Actual behaviour

202 is returned
There is a correct error code in OC-JobStatus-Location, but the request itself returns 202
same happens on other illegal operations, e.g. move without permission, rename to illegal names, etc.

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @PVince81.

Possibly related issues are #24509 (Async file operations), #235 (no http error code), #32594 ([WIP] [stable10] tests async operations), #2127 (WebDAV: MKCOL in non edit shared folder returns HTTP result code 201), and #11812 (Return generic HTTP errors from controllers).

[PVince81]

to be discussed with @DeepDiver1975

I think this is not critical

[DeepDiver1975]

This has been discussed already - pre processing can be done on the initial request.
Needs to be added in a followup PR -> not critical

@PVince81 you can assign me to this for the next sprint