[Bug - Edge Addons] Duplicate history entries generated on extension detail page when logged in, breaking Back button navigation

Describe the bug
When logged into a Microsoft account on the Microsoft Edge Add-ons store, navigating to any extension detail page creates multiple identical browser history entries in the background. As a result, clicking the browser's Back button fails to return to the previous page, as it only navigates through duplicate entries of the current page. Long-pressing the Back button reveals a stack of identical URLs for the same extension page.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home.
2. Log in with a Microsoft account.
3. Click on any extension to open its detail page.
4. Click the browser's Back button once.
5. See error: The page remains on the current extension detail page. (Long-press the Back button to view the duplicated history stack).

Expected behavior

• Clean Navigation: Clicking the Back button once should immediately return to the previous page (e.g., store homepage or search results) without generating redundant history entries.
• Session Persistence: The login session should be properly persisted across browser restarts, maintaining the logged-in state without requiring a re-login every time the browser is reopened.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Microsoft Edge / Google Chrome
• Version: Latest

Additional context

• Authentication Dependent: This issue only occurs when logged in to a Microsoft account. It does NOT reproduce when logged out.
• Cross-Browser & Extension-Free: Reproducible on both Edge and Chrome with all extensions disabled.
• InPrivate / Incognito: Does NOT reproduce in InPrivate/Incognito mode.
• History Stack vs UI: Standard browser history (Ctrl + H) deduplicates the entries into a single item, but the underlying browser history stack retains multiple duplicate entries, likely caused by history.pushState() executed during post-login session/auth verification.
• Passive Accumulation: User interaction is not required. Simply opening an extension page and waiting on it will silently accumulate 10+ duplicate entries in the background.
• UI Interference: When immediately long-pressing the Back button while the page is loading/authenticating, the history dropdown menu repeatedly flashes and closes itself due to real-time stack updates. Long-pressing after waiting a few seconds works stably, as the loop eventually hits a retry limit or browser throttling block.
• Side Note (Session Persistence Issue): The Edge Add-ons store also fails to persist the login state. Closing and reopening the browser forces a re-login every time (even though other Microsoft services remain signed in). This session handling issue might be closely related to the auth/cookie quirks mentioned above.