Add cooldown period between consecutive notifications

[jimmymadon]

Feature Description

Since the introduction of multiple recent features and modules, their new setup CTAs were all rendered simultaneously if their necessary feature flags and other conditions are met. This issue was fixed by refactoring each of these Setup CTAs into using the new Notifications "queue" infrastructure. However, like ordinary notifications, when a Setup CTA is actioned, the next in line Setup CTA will show immediately. This could cause "banner fatigue" with fewer users wanting to action banners that appear later on in the queue. (Internal Slack Discussion Thread)

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• All notifications (exceptions below), when viewed or actioned, should trigger a "cooldown period" of 15 minutes. During the cooldown period, no other notification (exceptions below) should be shown.
• The cooldown period will be triggered only after the rendering of all Warnings, Informative notices and Setup CTA Banners. The notification type column in the Banners Spreadsheet shows the types.
• Error notifications (e.g. auth error, internal server error) and "setup success subtle notifications" (e.g. when a feature or module is setup successfully) should behave the way they do now.
  • Errors should always be shown when they appear. These notifications will "block" other notifications that appear "behind" them.
  • Setup success subtle notifications are only ever shown once when the conditions of a successful setup are met. On any subsequent page reloads, these are never shown again. They should not trigger a cooldown period either.
• Once Issue Rotate notifications if not actioned #10106 has been merged along with this issue, the resultant effect will be as follows:
  • Example A: If there is only one notification in the queue and it has been viewed, it will not show again for 15 minutes. If it was actioned and dismissed, it's normal dismissal expiry time will apply.
  • Example B: If there are three notifications in the queue and the first one has been viewed, it will not be shown on page reload. The second notification will appear after 15 minutes (page reload will be required). Once viewed, no notification will be shown for 15 minutes. Then the third notification will appear. Once viewed, no notification will be shown for 15 minutes. Finally, the first notification will be shown again and the cycle repeats.

Implementation Brief

Test Coverage

QA Brief

Changelog entry

[aaemnnosttv]

@jimmymadon did we decide to make this issue dependent on #10106?

[jimmymadon]

@aaemnnosttv Yes sorry - just added that dependency now!