[tests-only][full-ci]Extend tests coverage for different role capability for group

[amrita-shrestha]

Description

This PR extends tests coverage for different role user capability over group manipulation
rename group will be implemented in ocis owncloud/web#7947.
As Viktor Scharf told 403 Forbidden vs 401 Unauthorized. I would be expect 403 code. But we definitely have chaos here and often for developers - 401 ok. in case non-existent - 404 or 403. looking at witch checking is first.

Related Issue

• API tests to grant a different appRoleAssigment to a user by graph API #5565

Motivation and Context

How Has This Been Tested?

• Locally

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[grgprarup]

LGTM 👍

[ownclouders]

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/20735/86/1

💥 To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20735/tracing/file-alice-2023-3-23-10-18-59.zip

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20735/tracing/multiple-spaces-can-be-managed-at-once-in-the-admin-settings-via-the-batch-actions-alice-2023-3-23-10-11-00.zip

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20735/tracing/space-members-can-be-invited-with-an-expiration-date-alice-2023-3-23-10-20-38.zip

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20735/tracing/space-members-can-be-invited-with-an-expiration-date-brian-2023-3-23-10-20-44.zip

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20735/tracing/user-group-assignments-can-be-handled-via-batch-actions-admin-2023-3-23-10-12-13.zip

[micbar]

@rhafer @butonic I think graph response codes are a real mess. we need to clean that up before we do more manifestations in covering that with tests.

[butonic]

In general here is a list of error codes returned by the ms graph api: https://learn.microsoft.com/en-us/graph/errors

Now the 401 Unauthorized vs 403 Forbidden vs 404 Not Found status code may look tricky, but hara are the guidelines:

• we don't want to expose existence of resources if a user has no access to them, so we return a 404 Not Found instead of a 403 Forbidden.
• when a user has access to a resource but tries to execute an action that he does not have enough permissions for, e.g. when he tries to write to a read only share, we return a 403 Forbidden

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information