Upgrade all packages to v0.10.0 - Synchronized versioning across all …

…packages

- Upgraded ElBruno.Realtime to v0.10.0
- Upgraded ElBruno.QwenTTS.Realtime to v0.10.0
- Upgraded ElBruno.Realtime.Whisper to v0.10.0
- Upgraded ElBruno.Realtime.SileroVad to v0.10.0
- Upgraded ElBruno.VibeVoiceTTS.Realtime to v0.10.0
- Upgraded ElBruno.KokoroTTS.Realtime to v0.10.0

All tests passing (56/56). Build clean with zero warnings/errors.

This release establishes the versioning rule: all packages in the ElBruno.Realtime repository maintain synchronized versions and are republished together to NuGet.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Release v0.1.1-preview: GPU configuration support for UseQwenTts()

Key changes:
- Added optional GPU device configuration callback to UseQwenTts()
- Users can now configure DeviceId for multi-GPU systems
- Example: .UseQwenTts(opts => opts.GpuDeviceId = 1)
- 11 new test cases covering all configuration scenarios
- Backward compatible — existing code works without changes

Resolves: #3

Merge pull request #2 from elbruno/squad/1-apply-localembeddings-audit

Apply security, performance & CI hardening from LocalEmbeddings audit (Issue #1)

Add ElBruno.KokoroTTS.Realtime bridge package

- Create KokoroTextToSpeechClientAdapter implementing ITextToSpeechClient
  wrapping KokoroSharp.CPU (Kokoro-82M, ~320MB ONNX model)
- Support auto-download with progress callback via LoadModelAsync
- Streaming support via GetStreamingSpeechAsync using channels
- Add KokoroTtsRealtimeExtensions with UseKokoroTts() and
  AddKokoroTtsRealtime() DI extension methods
- Add Kokoro as default TTS option [0] in scenario-04 console
- Show download progress inline during model download

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

feat: split Aspire sample into separate Voice Chat and Game frontends

Restructure scenario-03-blazor-aspire from 2 to 3 Aspire projects:
- scenario-04.Api: Shared backend (ConversationHub + GameHub) -- unchanged
- scenario-04.Web: Voice chat frontend only (Conversation.razor)
- scenario-04.Game: Side-scroller game frontend (Game.razor + game-engine.js) -- NEW

Both frontends connect to the same API backend via Aspire service discovery.
AppHost now registers api, web, and game as separate services.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

feat: split Aspire sample into separate Voice Chat and Game frontends

Restructure scenario-03-blazor-aspire from 2 to 3 Aspire projects:
- scenario-04.Api: Shared backend (ConversationHub + GameHub) -- unchanged
- scenario-04.Web: Voice chat frontend only (Conversation.razor)
- scenario-04.Game: Side-scroller game frontend (Game.razor + game-engine.js) -- NEW

Both frontends connect to the same API backend via Aspire service discovery.
AppHost now registers api, web, and game as separate services.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>