refactor: [M3-8331] - useToastNotification async toasts

[pmakode-akamai]

Description 📝

const toasts: Toasts = { ... }  should be moved to the event directory and map to event messages already defined in our new factory

Changes 🔄

• Refactor useToastNotification.
• Move const toasts: Toasts = { ... } to Events/asyncToasts.tsx.
• Map to event messages already defined in our new factory.

Target release date 🗓️

N/A

How to test 🧪

Verification steps

• Verify all the async toasts continue to work as expected.
• Confirm formatting and displaying of messages.

As an Author I have considered 🤔

Check all that apply

• [x] 👀 Doing a self review
• [x] ❔ Our contribution guidelines
• [x] 🤏 Splitting feature into small PRs
• [x] ➕ Adding a changeset
• [ ] 🧪 Providing/Improving test coverage
• [ ] 🔐 Removing all sensitive information from the code and PR description
• [ ] 🚩 Using a feature flag to protect the release
• [ ] 👣 Providing comprehensive reproduction steps
• [ ] 📑 Providing or updating our documentation
• [ ] 🕛 Scheduling a pair reviewing session
• [ ] 📱 Providing mobile support
• [ ] ♿ Providing accessibility support

[github-actions[bot]]

Coverage Report: ✅
Base Coverage: 86.2%
Current Coverage: 86.2%

[jdamore-linode]

@pmakode-akamai Hey Purvesh, just a heads up that this PR seems to be causing a handful of test failures -- at a glance they seem to be caused by toast notifications for certain events not appearing when Cloud expects them to appear

[pmakode-akamai]

@pmakode-akamai Hey Purvesh, just a heads up that this PR seems to be causing a handful of test failures -- at a glance they seem to be caused by toast notifications for certain events not appearing when Cloud expects them to appear

Hey Joe (@jdamore-linode), this PR is still WIP. I’ll be looking into the test failures related to the toast notifications and will address them soon. Thanks!