[tests-only][full-ci] add test to disable mail and in-app notifications when receiving a federated share

[prashant-gurung899]

Description

This PR adds test to disable mail and in-app notification for Share Received event for OCM.

Scenario: federated user disables mail and in-app notification for "Share Received" event

Related Issue

• Bug Report: [QA][OCM] no notification when receiving a federated share #10718
• Part of: [QA] Tests for disabling notification settings #10802

Motivation and Context

How Has This Been Tested?

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:

[PrajwolAmatya]

LGTM

[saw-jan]

is the tag required? and why?

[prashant-gurung899]

Yes because the email notifications from prior scenarios weren't cleaned up which made CI to fail.
The notifications were related to invitation/collaboration. See build: https://drone.owncloud.com/owncloud/ocis/43375/46/9

[0]=>
      │   object(stdClass)#4013 (9) {
      │     ["mailbox"]=>
      │     string(5) "brian"
      │     ["id"]=>
      │     string(20) "20250212T063355-0001"
      │     ["from"]=>
      │     string(47) "Alice Hansen via ownCloud <[email protected]>"
      │     ["to"]=>
      │     array(1) {
      │       [0]=>
      │       string(19) "<[email protected]>"
      │     }
      │     ["subject"]=>
      │     string(58) "ScienceMesh: {InitiatorName} wants to collaborate with you"
      │     ["date"]=>
      │     string(30) "2025-02-12T06:33:55.162188624Z"
      │     ["posix-millis"]=>
      │     int(1739342035162)
      │     ["size"]=>
      │     int(2737)
      │     ["seen"]=>
      │     bool(false)
      │   }

[saw-jan]

Then we should think of better solution again. Maybe do mailbox cleanup in the beforeScenario hook of scenarios that have @email tag?

CC @amrita-shrestha

[saw-jan]

This should be done in separate PR

[nabim777]

Except all the above comments, it LGTM 👍

[prashant-gurung899]

Holding this PR until this gets merged : #11011

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[saw-jan]

For now let's not block the PRs. we can merge with the tag and do cleanup when we have proper solution for clearing mails.