[release/10.0-preview4] Backport identity template fix.

[ilonatommy]

Partial backport of #61633 to release/10.0-preview4

Description

• Blazor identity templates (-auth Individual) were expecting NavigateTo to throw. We should remove this expectation for the new way of navigation.
• Blazor templates do not test behavior at runtime. That is why we did not catch this bug in the PR that changed the navigation flow. We have build and publish and check of produced elements on dotnet new command covered. I don't think we want to add runtime tests for templates, it would add a lot of testing and maintenance load, even if it was added to outerloop. Manual tests caught this problem. Fixes https://github.com/dotnet/AspNetCore-ManualTests/issues/3609.

Fixes #3609

Customer Impact

Customer code based on the template won't be throwing after each redirection because the exceptions located after each redirect action got removed. If the customer misuses the identity manager class, they won't notice if they call RedirectTo from non-static code.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

This is a change to templates only.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[javiercn]

We need to make this message more "human-friendly".

Alternatively, within OnIntializedAsync we can check RenderInfo.IsInteractive and potentially throw an exception there, or display an alternative UI with an error message (or redirect to the error page).

@MackinnonBuck since this affects the Identity UX it will be good if we can figure this out together.

Ultimately with the exception going away we need to provide an alternative, it might be throwing, redirecting to the error page or showing a message in this page.

[javiercn]

@MackinnonBuck just FYI, we might merge this to unblock things and do a follow up to cleanup things when we've had a chance to talk together through this.

[dotnet-policy-service]

Hi @@ilonatommy. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.