fix: harden docker deployment and monitoring hub URL resolution

[Foxlider]

Summary

This PR fixes Docker runtime issues and improves reliability when KAST is deployed behind reverse proxies or under a path base. It ensures required Blazor web assets are present in published images, cleans up container/network configuration and docs, makes SignalR hub URL construction path-safe for both monitoring components, persists Data Protection keys in production, updates package versions, and refreshes a test double to keep end-to-end tests stable.

---

Type of Change

• feat — new feature
• fix — bug fix
• perf — performance improvement
• refactor — code restructure, no behaviour change
• docs — documentation only
• chore / ci — build, tooling, dependencies
• Breaking change — existing behaviour changes (add ! to the PR title type)

---

What Changed

• Added publish-time guard in Dockerfile to fail image build if Blazor web assets are missing.
• Added RequiresAspNetWebAssets in KAST.UI project to guarantee web assets are included.
• Updated docker-compose networking and env setup:
• removed incorrect TCP publication for Arma game range
• documented UDP-only Arma game range usage
• added Kast__InternalBaseUrl for server-side hub calls
• Simplified and corrected nginx reverse-proxy config for Blazor/SignalR/API with proper upgrade and forwarded headers.
• Rewrote README Docker and Arma port documentation for clearer setup, port purpose explanation, and BattlEye RCon guidance.
• Expanded .dockerignore to reduce build context size/noise (git, IDE, artifacts, generated outputs, test results).
• Updated central package versions (ASP.NET/EF/OpenTelemetry/MudBlazor/test tooling) and added explicit SQLitePCLRaw package set.
• Updated hub URL construction in both NavMenu and MonitorTab to preserve path-base deployments and safely handle invalid/missing InternalBaseUrl.
• Added production Data Protection key persistence to /app/data/keys so protected browser data survives container recreation.
• Improved end-to-end test NoopAppEventBroadcaster event members with explicit add/remove accessors for safer test-double behavior.

---

Testing

• Existing tests pass (dotnet test)
• New tests added for the changed behaviour
• Manually tested — describe below if relevant

Manual/verification notes:

• dotnet test --no-build
• Result: total 160, failed 0, succeeded 160, skipped 0
• dotnet build KAST.UI.csproj --no-restore

---

Checklist

• PR title follows Conventional Commits format
• Targets the correct branch (develop for features, main for hotfixes)
• No unrelated changes mixed in (whitespace, refactors, unrelated fixes)
• EF Core migration included if any entity model changed
• I have read CONTRIBUTING.md