This changes the behavior to a probe only gets trigged if the total max allocated bitrate actually changed. Also adding helpful log dump flag to ramp up tests that was used to investigate the issue. Bug: chromium:894434 Change-Id: I907675b8fd5a339f838b07d433ecf837e312def1 Reviewed-on: https://webrtc-review.googlesource.com/c/105981 Commit-Queue: Sebastian Jansson <srte@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25212}