Pages that are re-executed should allow interactivity

[ilonatommy]

Do not skip Render Mode boundary for re-executions

Re-executed page components should have configurable render mode because typically re-executed page is used in the same places as page rendered by NavigationManager.NotFound(). By allowing interactivity in the latter but not supporting it in the former case, we introduce inconsistency.

Description

• In case of error handling and re-execution, we used to always apply SSR. It does not make sense from the consistency reasons mentioned above. Re-execution case gets removed from the "always SSR" processing. Its render mode resolution will follow the same logic as any other component's.
• The test for checking interactivity on re-executed pages was added.

Fixes #63963

[Copilot]

Pull Request Overview

This PR enables interactivity for re-executed page components to maintain consistency with pages rendered through NavigationManager.NotFound(). Previously, re-executed pages were forced to use SSR mode, creating an inconsistency in behavior.

Key Changes

• Removed the _isReExecuted condition that forced SSR mode for re-executed pages
• Updated the test to verify interactivity functionality on re-executed pages
• Enhanced the re-executed page component with interactive counter functionality

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
ReexecutedPage.razor	Added interactive server render mode and counter functionality to test interactivity
InteractivityTest.cs	Converted test to fact and added interactivity verification
EndpointHtmlRenderer.Prerendering.cs	Removed re-execution condition that forced SSR mode

[maraf]

Looks good to me

[ilonatommy]

/backport to release/10.0

[github-actions]

Started backporting to release/10.0: https://github.com/dotnet/aspnetcore/actions/runs/18385401724