Bug: Navigation Menu - Login Button Control: Link Includes A ReturnUrl Resulting In Navigating To ReturnUrl Loop (5.0.3 static SSR)

[thabaum]

Issue

Login menu button is broken once you visit the login page. User will be navigated to the set ReturnUrl in navigation which is the homepage for this example. Once navigated to the homepage and a user clicks this control again it results in navigation to the same page you just returned to in a loop resulting in the Login Button Control.
https://github.com/oqtane/oqtane.framework/blob/dev/Oqtane.Client/Themes/Controls/Theme/Login.razor

Steps to reproduce

1. Fire up VS with the latest dev 5.0.3 commit
2. Install and switch to static rendering runtime.
3. Click login, sends you to login page, click login while on that page you will notice the url as below, go to another page and notice that login url stays as shown resulting in not being able to access the login page using that menu button control.

Expected Behavior:

User will stay on login page when button is clicked. There is no need to set a return Url for the login button control while a user is visiting a page with a login UI page form component. In fact I can't think of a reason to ever include a return url on the Login button control. It should always navigate to the login page every time it is clicked.

Additional Context

1. The login ReturnUrl should be removed if it has one already prior to applying it for all render modes. I can make strings of them long inside the browser.
2. If you click on a button that navigates to the same page, the old return url value could stay the same or be cleared, along with keeping its ability to navigate to the page it is on instead of removing it and pretty much going to the homepage from login.
3. I have not tested results from child pages. However the profile button while logged in, and the login button while logged out can display these behaviors currently.