Do not validate non spec obu-size

[JoTurk]

Description

AV1 RTP packets shouldn't not include obu_size [1], When i rewrote the av1 depacketizer i added validation so if we receive packets with obu_size we would try to validate that this obu_size matches the actual size to reject invalid packets fast, but I guess some clients are so broken that they send obu_size in rtp and also that obu_size is incorrect (someone reported this in Discord), this fix isn't part of any spec packets shouldn't have obu_size anyway, this is more of trying to follow RFC-9413

Be strict when sending and tolerant when receiving.

The AV1 specification allows OBUs to have an optional size field called obu_size (also leb128 encoded), signaled by the obu_has_size_field flag in the OBU header. To minimize overhead, the obu_has_size_field flag SHOULD be set to zero in all OBUs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.59%. Comparing base (438d7da) to head (5a7ea12).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #353      +/-   ##
==========================================
+ Coverage   82.58%   82.59%   +0.01%     
==========================================
  Files          28       28              
  Lines        3428     3430       +2     
==========================================
+ Hits         2831     2833       +2     
  Misses        427      427              
  Partials      170      170              

Flag	Coverage Δ
go	82.59% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.