Instead of using AudioProcessing API directly With AudioProcessing constructing move into the PeerConnectionFactory it is possible TestPeer doesn't have direct access to audio_processing, yet it is not null. Bug: webrtc:369904700 Change-Id: I5a4a9453ea3a0c735da8953c9ae5d9046d4e3916 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/365585 Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/main@{#43240}