Update dependencies and fix Windows streaming for v2.2.2

[femidof]

Summary

• bump Broadcaster version metadata to 2.2.2
• update the React, Tailwind, Tauri JavaScript, Vite, ESLint, TypeScript, pkg, and Rust dependency graphs
• upgrade bundled FFmpeg per target with version-aware prebuild checks
• fix Windows destination publishing through RTMPS/443 and verify both relay backends on a native Windows runner
• pin patched transitive versions and repair npm 10 lock metadata used by Node 22 release CI

Windows streaming fix

• native RTMPS sockets now send TLS SNI and preserve rtmps:// in RTMP connect metadata
• new YouTube destinations use rtmps://a.rtmps.youtube.com:443/live2/ instead of RTMP on port 1935
• existing destinations using Broadcaster's old YouTube preset migrate automatically; custom YouTube URLs are unchanged
• Windows uses FFmpeg 8.0 from ffmpeg-for-homebridge@2.2.2
• release CI launches the packaged Windows sidecar and bundled FFmpeg, publishes synthetic H.264/AAC into Broadcaster, and requires actual media at a destination through both native and FFmpeg modes before packaging

Final native Windows run: https://github.com/femidof/Broadcaster/actions/runs/29264491239

• native relay: H.264/AAC, 9,702 bytes received
• FFmpeg relay: H.264/AAC, 72,611 bytes received
• all five platform dependency, sidecar, and FFmpeg build jobs passed

FFmpeg compatibility

• macOS ARM64/x64 uses FFmpeg 6.1.1 from ffmpeg-ffprobe-static@6.1.2-rc.1, verified with a macOS 12 deployment target
• Linux ARM64/x64 and Windows x64 use FFmpeg 8.0 from ffmpeg-for-homebridge@2.2.2
• sources are exact-version pinned and the build rejects missing or stale binaries
• the downloader uses portable Node filesystem cleanup and a disposable manifest, so it works on Windows and cannot mutate repository package metadata

Intentional compatibility ceilings

• node-media-server stays on the latest v2 release, 2.7.4; upstream documents v4 as protocol-incompatible with v2, and v4 retains process-global configuration that conflicts with simultaneous profile ports
• TypeScript stays on 6.0.3 because the latest typescript-eslint supports TypeScript below 6.1 and rejects TypeScript 7
• Node declarations stay on 22.20.1 to match the Node 22 pkg target and release workflow

Validation

• clean npm 10 npm ci in root and sidecar
• zero vulnerabilities from both npm audits
• RustSec scan: no vulnerable crates; advisory warnings remain in Tauri Linux GTK3/WebKit transitive dependencies with no available lockfile upgrade
• npm run build
• npm run lint
• seven sidecar unit/regression tests
• packaged sidecar builds and end-to-end native/FFmpeg relay tests on macOS and Windows
• cargo check --manifest-path src-tauri/Cargo.toml
• cargo clippy --manifest-path src-tauri/Cargo.toml with no warnings
• native 2.2.2 app, DMG, and updater archive generated locally with the final sidecar
• updater signature generation remains CI-only because TAURI_SIGNING_PRIVATE_KEY is stored in GitHub Actions