fix(webrtc): reduce PeerConnectionAnalyzer log verbosity during bad quality

[pallavibakale]

☑️ Resolves

• Fix Reduce verbosity of PeerConnectionAnalyzer logs #15034

🛠️ API Checklist

🚧 Tasks

When connection quality is bad, _logStats was called every second and logged the full 5-7 entry rtcStats history each time, causing heavy duplication in the logs.

Now only the new rtcStats entries (added since the last log) are printed on each subsequent bad check. When quality recovers, any remaining unlogged entries are flushed once so no data is missing.

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not possible
• 📘 API documentation in docs/ has been updated or is not required
• 🔖 Capability is added or not needed

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)