Finding issues with the combination of MSAL-React + Next.js 14 when using redirect for logins.

Everything works if I run the application "live"

When I export the app as a client bundle, though, I'm seeing exceptions when MSAL processes the redirect.

From what it looks like:
- Initial page load is OK
- MSAL sees that the user needs to sign in
- MSAL redirects to a Microsoft page for sign in
- The Microsoft page redirects back, with data sent in the URL
- MSAL grabs the data out of the URL
- Next.js overrides window.history.replaceState
- MSAL has a clearHash() function that attempts to clear the "#" from the URL
- clearHash() makes a call to window.history.replaceState
- Next.js calls applyUrlFromHistoryPushReplace() from the overridden window.history.replaceState
- applyUrlFromHistoryPushReplace attempts to access window.history.state.__PRIVATE_NEXTJS_INTERNALS_TREE
- window.history.state is null at that point, so an exception gets thrown

Note that I'm passing a custom NavigationClient to the MSAL instance that uses the Next.js router for navigateInternal, but that doesn't appear to be getting called in this flow.

I haven't yet figured out why it works live, but not in the exported build -- I suspect it's a timing issue and in the live build either:
- MSAL makes the call to window.history.replaceState faster than Next.js can override it
- Next.js is able to set the value of window.history.state before MSAL attempts to call replaceState

Not sure if this is an MSAL bug or a Next.js bug.

It seems like this could potentially be addressed with either (or both):
- A null check on the Next.js side
- Using the Navigation client for updating the URL on the MSAL side (to enable everything that modifies the URL to go through the Next.js router)