Re-enable remote loop visuals with throttled updates

[Copilot]

Remote loop visuals were disabled entirely (SetVisualUpdatesEnabled(false)) as a temporary workaround for severe slowdown during NINJAM sessions. This removes the workaround and re-enables visuals with proper rate-limiting.

Changes

• LoopRemote: 15 Hz visual throttle — Update() checks elapsed time before consuming the dirty flag. Deferred updates retain _modelDirty for the next tick rather than exchange-then-re-set.
• StationRemote: interval change-guard — SetRemoteInterval() early-outs when length, visual length, and position are all unchanged, eliminating redundant resize/dirty-flag work on each job tick.
• No geometry rebuild — the existing vertex-shader path (fixed mesh + 1D waveform texture + PBO double-buffer upload) means per-update cost is O(2048) decimation + texture upload. The throttle caps this at 15×/sec per loop.

void LoopRemote::Update()
{
    if (!_modelDirty.load())
        return;

    std::chrono::steady_clock::time_point now = std::chrono::steady_clock::now();
    double elapsed = std::chrono::duration<double>(now - _lastVisualUpdate).count();
    if (elapsed < (1.0 / _MaxVisualUpdateHz))
    {
        // Leave _modelDirty set so the update is retried next tick.
        _bufferBank.UpdateCapacity();
        _monitorBufferBank.UpdateCapacity();
        return;
    }

    _modelDirty.store(false);
    _lastVisualUpdate = now;
    Loop::Update();
}

Notes

• _MaxVisualUpdateHz (15.0) is tunable if real-world testing shows it's still too aggressive.
• allowUnchangedSkip in LoopModel::UpdateModel provides an additional early-out for playing-state loops where nothing has changed.
• Needs NINJAM session testing to confirm the throttle + vertex-shader path is sufficient.