Repair .NET 10 and MudBlazor migration

[magiccodingman]

Summary

• Migrated the solution’s broken MudBlazor APIs to MudBlazor 9.7 while preserving the existing application behavior.
• Reworked dashboard charts for the new generic chart model and options API.
• Updated dialogs to ShowAsync, nullable dialog results, and async dialog-result handling.
• Updated MudDataGrid server callbacks for cancellation tokens and current sorting APIs.
• Migrated file upload content, chips, grids, forms, and validators to their current component APIs.
• Replaced obsolete synchronous MudForm.Validate() calls with ValidateAsync() and removed async void event handling where encountered.
• Retargeted the TLS test project and test host packages to .NET 10.
• Updated the TLS workflow to restore its out-of-solution test project explicitly.
• Pinned SQLitePCLRaw.bundle_e_sqlite3 2.1.12 to remove the vulnerable 2.1.11 native SQLite dependency selected transitively by EF Core.

Validation

• dotnet restore TruthGate-IPFS.sln — successful
• dotnet build TruthGate-IPFS.sln --configuration Release --no-restore — successful with 0 errors
• dotnet test TruthGate-Web/TruthGate-Web.Tests/TruthGate-Web.Tests.csproj --no-restore --configuration Release — successful
• Existing TLS lifecycle GitHub Actions workflow — successful under .NET 10

Notes

• The remaining compiler warnings are pre-existing nullable, analyzer, duplicate-using, EF raw-SQL, and obsolete-crypto warnings outside the focused .NET 10/MudBlazor repair scope.
• No merge or deployment action is included; this PR targets magiccodingman/net10 for review.