Expose stats ID for use in interceptor factories

[mengelbart]

Description

We are already using the ID to access interceptors. If we expose it, we can store data per peerconnection in interceptor factories and give users an API to interceptors of a specific peerconnection.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.67%. Comparing base (7d8a700) to head (e11b089).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3249      +/-   ##
==========================================
- Coverage   82.87%   82.67%   -0.21%     
==========================================
  Files          80       80              
  Lines       11196    11196              
==========================================
- Hits         9279     9256      -23     
- Misses       1498     1515      +17     
- Partials      419      425       +6     

Flag	Coverage Δ
go	82.67% <100.00%> (-0.21%)	⬇️

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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[drshrey]

@JoeTurki just checking, does this method need to exist in peerconnection_js.go in order for consumers compiling to wasm to be able to access this method (and do we care)? I suspect the wasm build tests are passing because this is a new method, but checking whether it's ok to introduce a new public method here but not in the js/wasm equivalent file.

[JoeTurki]

Good question, we currently don't support stats API in wasm, it would be cool to provide a fallback for stats and pion's interceptor but it will be a lot of work, and we can't support everything.
Thank you.