Upgrade to Angular 20 and .NET 10.0

[Copilot]

Upgrades the application from Angular 11/.NET Core 3.1 to Angular 20/.NET 10.0 while preserving the non-standalone architecture.

.NET Backend (.NET Core 3.1 → 10.0)

• Migrated from Startup.cs to minimal hosting model in Program.cs
• Replaced Microsoft.AspNetCore.SpaServices.Extensions with Microsoft.AspNetCore.SpaProxy
• Updated SignalR hub mapping from UseSignalR() middleware to MapHub<T>() endpoint routing
• Enabled implicit usings for modern C# conventions

Angular Frontend (v11 → v20)

• Updated all core packages to Angular 20
• Replaced @aspnet/signalr with @microsoft/signalr v8.0.7
• Upgraded TypeScript (4.1 → 5.8), Bootstrap (4 → 5), rxjs (6 → 7)
• Explicitly marked all components/pipes as standalone: false to maintain non-standalone architecture
• Configured schematics in angular.json to default new components to non-standalone
• Removed incompatible mr-mr2 dependency, implemented custom SortPipe

// All components now explicitly non-standalone
@Component({
  selector: 'app-home',
  templateUrl: './home.component.html',
  standalone: false  // Required in Angular 20 to maintain module-based architecture
})
export class HomeComponent { }

SignalR Integration

SignalR client migration example:

// Before: @aspnet/signalr v1
import { HubConnection, HubConnectionBuilder } from "@aspnet/signalr";

// After: @microsoft/signalr v8
import { HubConnection, HubConnectionBuilder } from "@microsoft/signalr";
// API remains compatible, no logic changes required

Security

Production dependencies: 0 vulnerabilities. Dev-only vulnerability in @angular/cli dependency does not affect deployed application.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Upgrade</issue_title>
<issue_description>We need to upgrade this project latest technology. Probably Angular 20 and .NET8.0. Possibly maybe .NET10.0</issue_description>

<agent_instructions>Upgrade Client app and depencies to Angular 20.
Keep the application as a non-standalone app. Also remember that in Angular standalone is standard, so we must explicitly mark components etc. as non-standalone.

Also upgrade the .NET Application as far as possible. Maybe NET8.0 or NET9.0 - but even better if we can make it to NET10.0

Also make sure that SignalR still works after the upgrade.
</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Upgrade #1

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.