VPR-54 fix(scheduler): render Razor 403 view for dashboard auth denials

Hangfire's dashboard middleware writes a bare 403 directly to the
response when our IDashboardAuthorizationFilter returns false, which
bypasses cookie auth's AccessDeniedPath and lands the user on the
browser's default error page. Add UseStatusCodePagesWithReExecute so
any bare 4xx/5xx status code re-runs through HomeController.Error and
the existing /Views/Home/403.cshtml view.

Applies globally — also catches stray bare 404s from any other
middleware. Status code is preserved on the response (browser still
sees 403); only the body is replaced with the rendered view.

Author: rlorenzo

web/Program.cs

@@ -388,6 +388,11 @@ void RegisterDbContext<TContext>(string connectionStringKey) where TContext : Db
 
     }
 
+    // Re-execute bare status-code responses (403, 404, etc.) through HomeController.Error
+    // so middleware that writes raw status codes — e.g. Hangfire's dashboard middleware
+    // when our auth filter denies — gets the same Razor error view as the rest of the app.
+    app.UseStatusCodePagesWithReExecute("/Error/{0}");
+
     // In development, set up Vite proxy BEFORE rewrite rules so it can handle .ts/.js files
     if (app.Environment.IsDevelopment())
     {