fix: resolve notification provider issue with react-router-dom upgrade for good

[mas-who]

Done

• This is a sister PR for the react-components fix in NotificationProvider. Instead of calling useLocation in NotificationProvider, we will now pass the returned state and pathname as props to the provider component.
• Upgraded react-router-dom to 6.21.3

QA

1. Run the LXD-UI:
   • On the demo server via the link posted by @webteam-app below. This is only available for PRs created by collaborators of the repo. Ask @lorumic or @edlerd for access.
   • With a local copy of this branch, run as described here.
2. Perform the following QA steps:
   • Wait until the react component PR gets merged, then check that queued notifications still work.

[webteam-app]

Demo starting at https://lxd-ui-614.demos.haus

[edlerd]

There's only a single use case of this and we don't expect more, so why not include the changes directly in the Root component?
Similar solution in #616

[mas-who]

There's only a single use case of this and we don't expect more, so why not include the changes directly in the Root component? Similar solution in #616

It was just a personal preference, since only notification provider needed state and path from useLocation I decided to keep it close to notification provider instead of Root. But your approach makes more sense 👍

[mas-who]

Closing this PR as the same issue was addressed by PR #616