Fix notification-section tests

[mcbouslog]

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

Fixes issue noted with recent PRs CI testing on node v20.10.0. The NotificationSection tests were providing a non-iterable value for an item that the component needs to be iterable.

This issue reminded me notifications would benefit from a refactor like #6815 or similar.

Describe your changes.

• refactor tests with props and state values such that component doesn't error when shallow rendered for tests

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?

[coveralls]

coverage: 56.999% (-0.06%) from 57.057%
when pulling 63057e1 on fix-notification-section-tests
into 304aa9a on master.

[goplayoutside3]

Looks good!