[sean0407]

Summary

Use the configured connectionIdLength when serializing a QUIC Preferred Address, so callers can control the advertised length independently of the connection ID bytes.

Evidence

• Reproduction: construct a Preferred Address with a two-byte connection ID, set connectionIdLength to 3, and serialize it. Before the fix, the advertised length byte is 2; the focused regression test failed with expected: <3> but was: <2>.
• Changed files:
  • TLS-Core/src/main/java/de/rub/nds/tlsattacker/core/protocol/message/extension/quic/QuicTransportParametersExtensionMessage.java
  • TLS-Core/src/test/java/de/rub/nds/tlsattacker/core/protocol/message/extension/quic/QuicTransportParameterTest.java
• Checks: focused Maven test passed (3 tests, 0 failures/errors); git show --check passed; patch policy accepted 2 text files and 21 changed lines.

Merge Danger

The wire length byte now follows the explicitly configured field when it differs from the payload array length. This is the behavior required to serialize intentionally modified protocol values; ordinary values where the lengths match are unchanged.

Fixes #247.