Fix removeToastNotification to use previousState

[aaronknol]

Important: Request PR reviews on Slack

Please reach out to the design system team on Slack in #prod_design_system for PR reviews. GitHub notifications (e.g. from tagging a person) are not actively monitored.

Why

When we had multiple toast's on a page, all with different id's, calling removeToastNotification would remove all toast's after the one that was being deleted.
The toast's all have a button inside them that when clicked will call removeToastNotification.
This is a similar problem to what we were having with addToastNotification which we fixed here

What

New

By using the previousState syntax of setState, the notifications in the removeToastNotification is always updated and correct.

setNotifications(prev => prev.filter(({ id }) => id !== notificationID))

Old

It appears that the copy of the state that was being created wasn't correct, it hadn't been updated yet before being sliced.

const copy = notifications.slice()
    copy.splice(notificationIndex, 1) // Mutation
    setNotifications(copy)

[changeset-bot]

🦋 Changeset detected

Latest commit: 7af4bf3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@kaizen/components	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

✨ Here is your branch preview! ✨

• Storybook

Last updated for commit 7af4bf3: Merge branch 'main' into remove-toast-notification

[mcwinter07]

Nice, it even looks cleaner than the original method of splicing it out 👍 Cheers for the contribution @aaronknol