Add Net.CreateListenConfig

[rg0now]

Description

Wrap net.ListenConfig to allow customizing vnet Listeners.

Reference issue

Related pion/turn#514

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.25%. Comparing base (37ee413) to head (eb98700).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #373      +/-   ##
==========================================
- Coverage   84.34%   84.25%   -0.09%     
==========================================
  Files          41       41              
  Lines        3194     3208      +14     
==========================================
+ Hits         2694     2703       +9     
- Misses        359      363       +4     
- Partials      141      142       +1     

Flag	Coverage Δ
go	84.25% <100.00%> (-0.09%)	⬇️

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.

[JoTurk]

@rg0now is it possible to fix the API compatibility? maybe we should keep transport.Net unchanged and introduce the option as an extension interface.

[rg0now]

@JoTurk I agree API breakage would be best to avoid. Here is a typical point where we want to use this. The idea is that we create a custom net.ListenConfig with the required sockopts applied and then call ListenPacket on that, and we want to do this all via transport.Net. Without this change we have to hard-code net.ListenConfig.

How to make this work? Do you have a concrete suggestion? Happy to redo this

[Sean-Der]

@JoTurk I think it might be ok! If we bump pion/transport it is just used internally by pion libraries. I don't think it should bother users too much.

Sorry if I put lots of anxiety on people around major version dumps. It's just a bummer that more people still use v3 vs v4. 2x more still import v3 and would love to fix that :'(

https://pkg.go.dev/github.com/pion/webrtc/v3
https://pkg.go.dev/github.com/pion/webrtc/v4

[JoTurk]

Yeah i was a semver absolute with my comment, there are work arounds but they are all seems to be ugly.

[Sean-Der]

@rg0now @JoTurk 👍 for me you both ok with merging + new major version? I can make sure all the deps get bumped :)

[rg0now]

@JoTurk @Sean-Der Please merge & bump version, I'm dangerously unreliable when it comes to release engineering

[JoTurk]

@rg0now Ok. I'm merging #370 and then i'm going to merge this and do major version bump, will go and upgrade it everywhere :)

[JoTurk]

@rg0now @Sean-Der we have few soft deprecated apis, since we're doing a major bump I'm going to open a PR right now to remove them.

[JoTurk]

Released in https://github.com/pion/transport/releases/tag/v4.0.1