[QA] test cases for enabling and disabling sharing roles

[saw-jan]

Some tests for enabling roles have been added

• [QA] Extend test for new sharing role space editor without version #10090
• [QA] run secure-viewer role tests with @env-config #10075

These test cases would be good to have:

• pre-condition: enable role -> share -> disable role

• roles to check: Secure Viewer, Editor Without Version, Denied

• check share
  From comment

  maybe we should assert these in a single scenario for these kinds of tests (edge-cases):

  • sharedByMe (sharer)
  • sharedWithMe (sharee)
  • list me/drives (sharee)
  • PROPFIND Shares space (sharee)
  • some action by sharee (e.g.: download file)

  • drives list [tests-only][full-ci]added test to list drives after the share role has been disabled #10756
  • sharedWithMe [tests-only][full-ci]added test to list shares sharedWithMe after the share role has been disabled #10744
  • sharedByMe [tests-only][full-ci] added test to list shares sharedByMe after the share role has been disabled #10752
  • delete share [tests-only][full-ci] added test to remove access to share after the share role has been disabled #10759 [tests-only][full-ci]added test to delete share access from group after the share role has been disabled #10798
  • update share to existing role [tests-only][full-ci] added test to update share role to existing role after the assigned share role is disabled #10760

• federated share [tests-only][full-ci] added test to enable disable Secure Viewer permissions role for federated shares #10823 [OCM] User can share resource to federated user with permission roles that is not allowed #10824

• disabling of default roles(editor) from comment. [tests-only][full-ci] added test to list shares after disabling Editor role #11057

• share after disabling role from comment [tests-only][full-ci]added test to share resources after the permissions role is disabled #11074

[PrajwolAmatya]

• federated share

For the federated share the permissions roles get filtered. For instance, if trying to share a file to a federated user by enabling all the permissions role, the available roles are Can View and Can Edit. The additional roles like Secure Viewer is not available.
UI only shows the two roles but the sharing is possible via API, and it is reported here #10824

[PrajwolAmatya]

For federated share, the roles gets filtered and only two permissions role Can View and Can Edit are available. This behavior is seen in the web UI as well as only two roles will be available even if all the roles are enabled.
But with API, resources are able to be shared with Secure Viewer. The behavior is different in UI and via API and there has not been confirmation whether current behavior is valid or should the behavior should be same as in UI. So, currently this issue is moved to blocked.
Reported issue: #10824