fix: correct statuscode and message when MOVEing between cross spaces

[saw-jan]

This PR changes the 502 statuscode to 403 with correct message while MOVEing between cross spaces.

Fixes:

• MOVE a file from Project space (manager/editor) to Project space (manager/editor) returns 502 code owncloud/ocis#8116
• MOVE a file from Project space (manager/editor) to Personal space returns 502 code owncloud/ocis#7618
• sharee (editor role) MOVE a file by file-id into Personal space responds with 502 instead of 403 owncloud/ocis#8124
• sharee (editor role) MOVE a file by file-id into Project space (manager/editor role) responds with 502 instead of 403 owncloud/ocis#8125

BUT there is this note in the code:

WebDAV RFC https://www.rfc-editor.org/rfc/rfc4918#section-9.9.4 says to use
502 (Bad Gateway) - This may occur when the destination is on another
server and the destination server refuses to accept the resource.
This could also occur when the destination is on another sub-section
of the same server namespace. but we only have a not supported error

Q: What should we expect in test? 502 or 403?
CC @micbar @kobergj

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[butonic]

The RFC is always right.

[saw-jan]

The RFC is always right.

Yeah,
But we recently changed 502 to 403 in most cases like MOVE between two shares, shares to personal and others

Scenarios matrix table is here: owncloud/ocis#8121

[micbar]

Needs to be 403 because of the oc10 compatibility.

[saw-jan]

Needs to be 403 because of the oc10 compatibility.

So does that mean this PR is valid? Should we change 502 to 403?

[micbar]

@TheOneRing @dragotin

We need to discuss. RFC is very clear.

[saw-jan]

From owncloud/ocis#4087 (comment)

The return status will be 502 Bad Gateway according to WebDAV spec. This fix is already in reva.

[saw-jan]

502 is the expected behavior
Ref: owncloud/ocis#8063 (comment)

So closing this PR