feat: rust webrtc implementation with libdatachannel

[damonhayhurst-neuraco]

Features

• flag-gated implementation of peer to peer streaming implementation in rust using libdatachannel and rust wrapper libdatachannel-rs
• renegotation of media channels versus ancestral reset of communications in aiortc
• fan out communication to N consumers

Relevant PRs

neuracore_frontend/368 - feat: rust webrtc implementation for frontend

[github-actions]

Consider updating changelogs/pending-changelog.md with a summary of this change for the release notes. This is optional and non-blocking.

[github-actions]

Code freeze: merging is blocked

One or more nightly integration test suites are failing, so feature PRs across the core repos are blocked from merging until every suite is green again. Live status: CI dashboard.

Failing workflows:

• Integration ML - Algorithm Performance Evaluate (Production) (neuracore, production)
• Integration ML - Algorithm Performance Evaluate (Staging) (neuracore, staging)
• Integration ML - Training Flow (Production) (neuracore, production)
• Integration PF - Importer (Production) (neuracore, production)
• Integration PF - Importer (Staging) (neuracore, staging)
• Integration ML - Back To Back Training (Staging) (neuracore, staging)
• Integration ML - Inference (Staging) (neuracore, staging)
• Integration ML - Resume Training (Production) (neuracore, production)
• Integration ML - Resume Training (Staging) (neuracore, staging)
• Integration ML - Dataset Mutation Training (Production) (neuracore, production)
• Integration ML - Dataset Mutation Training (Staging) (neuracore, staging)
• Integration PF - Data Daemon (Production) (neuracore, production)
• Integration PF - Data Daemon (Staging) (neuracore, staging)
• Integration PF - User Flow (Production) (neuracore_backend, production)

How this unblocks

• The freeze lifts automatically: this check re-runs every 30 minutes and on any label change. Once the failing suites pass (tonight's scheduled run, or a manual re-run of the failing workflow after a fix lands), the block and this comment are removed.
• The dashboard's default view tracks nightly scheduled runs only, so it can still show red for a while after a manual re-run has already lifted the freeze.
• To force an immediate re-check, run the Code Freeze workflow in this repo from the Actions tab (Run workflow).

Shipping a fix for the outage itself? Add the type:hotfix label to this PR and it is exempt from the freeze. Use it only for changes that fix or mitigate the failing tests or a production incident, not to land regular features during a freeze. Hotfix PRs are flagged in the release notes.