[release/10.0] Pages that are re-executed should allow interactivity

[github-actions]

Backport of #63964 to release/10.0

/cc @ilonatommy

Pages that are re-executed should allow interactivity

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

Customer Impact

Reported by a customer.

Regression?

• Yes
• No

No, we did not have not found re-exec feature before.

Risk

• High
• Medium
• Low

We start treating re-executed pages same way as any other page we render.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.3

• Make necessary changes in eng/PatchConfig.props