Add CreateScopeForStatusCodePages to Blazor templates

[Copilot]

This PR adds UseStatusCodePagesWithReExecute with the createScopeForStatusCodePages parameter to the Blazor Web template, restoring functionality that was removed in PR #62624 due to CI issues with SDK versions.

Changes

Added a single line to the Blazor template's Program.cs file:

app.UseStatusCodePagesWithReExecute("/Error", createScopeForStatusCodePages: true);

Implementation Details

• Location: Added in the non-development environment configuration block, after UseExceptionHandler and before UseHsts
• Route: Uses the existing /Error page (same as the exception handler)
• Parameter: Uses the new createScopeForStatusCodePages: true parameter name (renamed from the previous parameter)
• Middleware Order: Follows ASP.NET Core pipeline conventions (exception handling → status code pages → security → protocol)

Verification

• Template builds successfully without compilation errors
• Only the BlazorWeb server template requires this change (BlazorWeb Client is WebAssembly-only)
• No other project templates currently use StatusCodePages middleware
• Change is minimal and surgical (single line addition)

The implementation enables proper service scope creation for status code page handling in Blazor applications, matching the pattern already used for exception handling with createScopeForErrors: true.

Fixes #62842.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[dotnet-policy-service]

Greetings human! You've submitted a PR that modifies code that is shared with https://github.com/dotnet/runtime . Please make sure you synchronize this code with the changes in that repo!

[ilonatommy]

the failure is #62851