Add QUIC transport parameters as a TLS extension

[kayoch1n]

Checklist:

• If you are new to Scapy: I have checked CONTRIBUTING.md (esp. section submitting-pull-requests)
• I squashed commits belonging together
• I added unit tests or explained why they are not relevant
• I executed the regression tests (using cd test && ./run_tests or tox)
• If the PR is still not finished, please create a Draft Pull Request

This PR is NOT an implementation of QUIC. Instead, it adds the QUIC transport parameters as a TLS exntension, which has an extension type of 57(0x39)

[codecov]

Codecov Report

Attention: Patch coverage is 95.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 78.73%. Comparing base (a8583a5) to head (0f3622d).
Report is 7 commits behind head on master.

Files with missing lines	Patch %	Lines
scapy/layers/tls/quic.py	94.82%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4614      +/-   ##
==========================================
- Coverage   81.38%   78.73%   -2.66%     
==========================================
  Files         359      335      -24     
  Lines       86029    80950    -5079     
==========================================
- Hits        70017    63735    -6282     
- Misses      16012    17215    +1203     

Files with missing lines	Coverage Δ
scapy/layers/tls/extensions.py	84.04% <100.00%> (+0.14%)	⬆️
scapy/layers/tls/quic.py	94.82% <94.82%> (ø)

... and 285 files with indirect coverage changes

[gpotter2]

Cool PR. Sorry for the delay.

To give some context, I have a PoC implementation of the structures in rfc9000 that I need to push, and I was thinking we could merge some parts regarding the variable int fields.

Sorry, currently in holidays and don't have access to it right now, but I'll make sure to get back to it as soon as I come back.

Thanks