Allow a "permission denied error" from reva to bubble up to the client.
Reva was fixed to return "permission denied" only when the space to be
delete can actually be listed by the user. Other wise it will return
"not found". See reva commit 1bf72cb76394671f373e87f15f23f978cf41ab08.
So when a user with the 'can manage' role tries to purge an already
disabled space it will now get "Forbidden" status instead of a "Not
found".
Also fixes the expected status codes in the tests.
(cherry picked from commit 99d80f30a9)
* resharing.feature: Used sharingNG for sharing in given step
* unlockFiles.feature: Used sharingNG for sharing in given step
* apiSpacesShares suite: Used sharingNG for sharing in given step
* acceptShares.feature: Used sharingNG for sharing in given step
* uploadFile.feature: Used sharingNG for sharing in given step
* coreApiWebdavUploadTUS suite: Used sharingNG for sharing in given step
* tag.feature: Used sharingNG for sharing in given step
* coreApiShareOperationsToShares2 suite: Used sharingNG for sharing in given step
* updateShare.feature: Used sharingNG for sharing in given step
* Fixed line numbers in expected failure
* update given step using sharingNg in restoreSpaces.feature
* update given step using sharingNg in setQuota.feature
* update given step using sharingNg in tag.feature
* update given step using sharingNg in trashBin.feature
* update given step using sharingNg in tusUpload.feature
* update given step using sharingNg in uploadSpaces.feature
* update given step using sharingNg in changeSpaces.feature
* update given step using sharingNg in disableAndDeleteSpaces.feature
* update given step using sharingNg in editPublicLinkOfSpace.feature
* update given step using sharingNg in filePreviews.feature
* update given step using sharingNg in listSpaces.feature
* update given step using sharingNg in publicLink.feature
* update given step using sharingNg in removeSpaceObjects.feature
* refactor given/when/then steps in spaces context
* pass the returned response without setting in then step
* added the missing when step whose response is checked by the then step
* addressed the reviews
* changed from decoded body to docoded response
* refactored given steps
* refactored some when stepa
* refactored remaining when and then steps
* use of when step for the action
* changed line no in expected failure
* remove and add same kind of steps in the scenario and refactored function names
* adressing reviews
* use default config for OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY
* remove unnecessary steps
* use default propfind depth infinity value
* use correct step to check the resources
* use correct step to check the resources
* cover depth:infinity enabled test cases
* fix steps
* fix scenario steps
* update expected failure list
* add depth infinity test suite to ci
* update existing tests only
* remove test with depth:infinity