[FEATURE] Muting core log messages like "Unable to parse msg received from"

[denyspozniak]

Hello!
I propose to create some mechanism for disable/mute logs from the core when receiving a corrupted sip message such as:

ERROR:core:parse_msg: message=<>
ERROR:core:receive_msg: Unable to parse msg received from [[1.1.1.1:40327](http://1.1.1.1:40327/)]
ERROR:core:parse_to_param: unexpected char [,] in status 29: <<;tag=tmnb>> .
ERROR:core:get_hdr_field: bad to header

[denyspozniak]

@bogdan-iancu I'm not sure if this issue falls under a similar problem, but I would be very happy if it does.
we have a number of problematic user-agents that send us 200 OK special symbols in the To tag.

opensips[3850953]: Jul  4 13:08:56 [3850953] ERROR:core:parse_to_param: unexpected char [,] in status 29: <<;tag=tmnb>> .
opensips[3850953]: Jul  4 13:08:56 [3850953] ERROR:core:get_hdr_field_aux: bad to header
opensips[3850953]: Jul  4 13:08:56 [3850953] ERROR:core:parse_msg: message=<SIP/2.0 200 OK
opensips[3850953]: Via: SIP/2.0/UDP 3.3.38.33:5060;branch=z9hG4bKfa11.246c3716.0;cid=1
opensips[3850953]: Via: SIP/2.0/UDP 3.3.36.15:5060;rport=5060;received=3.3.36.15;branch=z9hG4bK4414702
opensips[3850953]: From: <sip:pinger@3.3.36.15>;tag=uloc-1a-684df4b8-488-87dd01-21252621-bad43503
opensips[3850953]: To: <sip:q8bil6hr7c8h@3.3.36.130:5060>;tag=tmnb,0`,795eg5c9,599,96ee10,30343730,c`e52412
opensips[3850953]: Call-ID: 40b0ec64-b30eab71-1ed0ad1@3.3.36.15
opensips[3850953]: CSeq: 1 OPTIONS
opensips[3850953]: Supported: replaces
opensips[3850953]: Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
opensips[3850953]: Accept: application/sdp,application/dtmf-relay,application/simple-message-summary,message/sipfrag
opensips[3850953]: Accept-Encoding: identity
opensips[3850953]: Accept-Language: en
opensips[3850953]: Content-Length: 0
opensips[3850953]: #015
opensips[3850953]: >