fix(webrtc): turn down the webrtc log spam

[dhuseby]

Description

This PR changes a couple tracing::error!'s to tracing::warn!'s in the
webrtc code so that it won't spam the log so much. The error messages are still
available if you run your app with RUST_LOG=warn but if you run with the
default error level you will no longer get spammed.

Notes & open questions

Nope.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• A changelog entry has been made in the appropriate crates

Signed-off-by: Dave Grantham [email protected]

[jxs]

Hi Dave, thanks for this, but I don't think it makes sense to turn down logging level just to avoid them not outputting as the default RUST_LOG level is error, these are in fact errors.
Specially as I think when the code reaches these errors the connection has reached an unrecoverable state right?

[elenaf9]

@dhuseby if these errors occur very frequent in your logs then it might be an indication of bigger underlying issue. Could you provide some debug-level logs where this error appears?

The function is used in the initial noise handshake, so might be related to #5877.