[tests-only][full-ci] refactor scenarios to remove multiple listAllNotifications request in steps

[prashant-gurung899]

Description

This PR refactors the notifications test scenarios such that there are no multiple steps that requests to list all the in-app notifications
Originated from: #10928 (comment)

In some notification test scenarios, we were using steps like follow:

When user "Brian" lists all notifications
Then the HTTP status code should be "200"
And user "Brian" should get a notification with subject "Space shared" and message:

In this case, listing all notifications request(listAllNotifications) was called twice.

Related Issue

• Part of: [QA] Notification settings Tests #10802

Motivation and Context

How Has This Been Tested?

• Locally
• CI

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:

[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

[amrita-shrestha]

lgtm