Staging branch URL: https://pr-6815.pfe-preview.zooniverse.org

Closes #6793 . Issue summary - the NotificationsPage is requesting 50 notifications then grouping into project/Zooniverse sections. If a user has a notification from a project not included in the 50 notification response, then that project and related notification(s) will not show.

Describe your changes.

• refactor NotificationsPage and NotificationSection to remove componentWillMount and componentDidMount
• request all notifications from NotificationsPage
• refactor NotificationSection to remove notification requests (all notifications are requested in and passed down from NotificationPage)
• update and add tests per refactors

DMed user that noted issue in Talk, confirmed with staged branch that issue is resolved.

Let me know if you'd like me to mention your username in Talk somewhere or comment on a Discussion your subscribed to, so you have unread (delivered: false) notifications.

Note: initially refactored as functional component, but had issues with tests, ended up keeping as class component to maintain (ended up increasing) test coverage. Not ideal and open to suggestion, but I think ok based on limited time to refactor PFE.

Based on my notifications (127 Zooniverse, 1 NfN Big Bee Bonanza, 1 test project)
Comparison of https://talk.zooniverse.org/notifications? requests from NotificationsPage and NotificationSection:

CURRENT:

• load https://www.zooniverse.org/notifications (Note - missing test project project => issue linked)
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=50
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=1&delivered=false&section=zooniverse
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=1&delivered=false&section=project-18522 // NfN Big Bee Bonanza
• expand Zooniverse section
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=5&section=zooniverse
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=1&delivered=false&section=zooniverse
• expand project section
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=5&section=project-18522
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=1&delivered=false&section=project-18522

PR/CHANGES

• load https://pr-6815.pfe-preview.zooniverse.org/notifications (includes my test project notification)
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=1&page_size=50
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=2&page_size=50
  • https://talk.zooniverse.org/notifications?http_cache=true&admin=true&page=3&page_size=50
• expand Zooniverse section
  • none
• expand project section
  • none

Required Manual Testing

• Does the non-logged in home page render correctly?
• Does the logged in home page render correctly?
• Does the projects page render correctly?
• Can you load project home pages?
• Can you load the classification page?
• Can you submit a classification?
• Does talk load correctly?
• Can you post a talk comment?

Review Checklist

• Does it work in all major browsers: Firefox, Chrome, Edge, Safari?
• Does it work on mobile?
• Can you npm ci and app works as expected?
• If the component is in coffeescript, is it converted to ES6? Is it free of eslint errors? Is the conversion its own commit?
• Are the tests passing locally and on GitHub Actions?

Optional

• Have you replaced any ChangeListener or PromiseRenderer components with code that updates component state?
• If changes are made to the classifier, does the dev classifier still work?
• Have you resized and compressed any image you've added?
• Have you added in flow type annotations?
• Have you followed the Springer guidelines for commit messages?