Clear hash only if it contains known properties

[tnorling]

handleRedirectPromise clears the current hash before processing the redirect response. Today this logic doesn't care if the hash came from the current url or from the cache. This causes problems for hash routing scenarios where a custom (non-msal) hash may be removed, causing a route change before the hash can be processed.

This PR fixes this behavior by only clearing the current hash if it contains known response properties

Fixes #4400

[codecov-commenter]

Codecov Report

Merging #4415 (6808be4) into dev (7dd8b32) will not change coverage.
The diff coverage is 100.00%.

Flag	Coverage Δ		*Carryforward flag
msal-angular	96.39% <ø> (ø)
msal-browser	87.50% <100.00%> (ø)
msal-common	85.37% <ø> (ø)		Carriedforward from 7dd8b32
msal-core	82.65% <ø> (ø)		Carriedforward from 7dd8b32
msal-node	80.72% <ø> (ø)		Carriedforward from 7dd8b32
msal-node-extensions	76.03% <ø> (ø)		Carriedforward from 7dd8b32
msal-react	94.27% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files	Coverage Δ
...l-browser/src/interaction_client/RedirectClient.ts	100.00% <100.00%> (ø)

[ghost]

🎉@azure/msal-browser@v2.22.0 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes
• Official NPM Release