JitterBuffer: Improve performance for SampleBuilder use

[thatsnotright]

Description

This PR Should hopefully improve the performance for use by SampleBuilder and in the general case.

@at-wat If you have time would you be able to test this PR and the corresponding branch I created in the webrtc repository? pion/webrtc#2959

Thank you!

[codecov]

Codecov Report

Attention: Patch coverage is 80.40936% with 67 lines in your changes missing coverage. Please review.

Project coverage is 69.37%. Comparing base (d34a3c5) to head (8e20454).
Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
pkg/jitterbuffer/priority_queue.go	80.96%	51 Missing and 8 partials ⚠️
pkg/jitterbuffer/jitter_buffer.go	20.00%	4 Missing ⚠️
pkg/jitterbuffer/receiver_interceptor.go	81.81%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #292      +/-   ##
==========================================
- Coverage   72.87%   69.37%   -3.50%     
==========================================
  Files          80       80              
  Lines        3679     4693    +1014     
==========================================
+ Hits         2681     3256     +575     
- Misses        865     1287     +422     
- Partials      133      150      +17     

Flag	Coverage Δ
go	?
wasm	69.37% <80.40%> (-1.11%)	⬇️

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.

[at-wat]

I'll try it later!

[at-wat]

@thatsnotright I tested this branch locally in my usecase and confirmed that SampleBuilder's performance is good! (mostly same CPU/memory usage as the latest release)

[thatsnotright]

@thatsnotright I tested this branch locally in my usecase and confirmed that SampleBuilder's performance is good! (mostly same CPU/memory usage as the latest release)

@at-wat Thank you for taking the time to test, I appreciate your time! I'll clean up the code a little and make some test coverage improvements and then work with @Sean-Der on next steps!