Promote QUIC support to stable

[lucassaldanha]

This ticket captures all the necessary work to promote QUIC from experimental to a stable feature.

Plan

1. Release jvm-libp2p 1.3.4 with all required fixes for QUIC.
2. Update teku master --Xp2p-quic-enabled to default to true (26.7.0)
3. Deploy to hoodi nodes for soaking
4. After the release, once we are happy with how things are going using QUIC, we can completely remove the feature flag --Xp2p-quic-enabled and clean-up some of our CLI options.

Tasks (now)

• Confirm libp2p preference (QUIC > TCP)
• Update teku to use jvm-libp2p 1.3.4 + --Xp2p-quic-enabled to default to true on master
• Update our docker files to add UDP 9001
• Deploy to Hoodi nodes
• Rename --Xp2p-quic-port and --Xp2p-quic-port-ipv6 to --p2p-quic-port and --p2p-quic-port-ipv6
• Rename --Xp2p-advertised-quic-port and --Xp2p-advertised-quic-port-ipv6 to --p2p-advertised-quic-port and --p2p-advertised-quic-port-ipv6
• Update docs (including notes about new firewall rules required for UDP port (QUIC)
• We need to add a note about this in the release notes

Testing/Soaking

Deploy our whole fleet of nodes and soak for 72h+. Check we have both inbound/outbound quic conns and also that native memory usage is stable (no more leaks).

[lucassaldanha]

This requires jvm-libp2p 1.3.3 (with this PR libp2p/jvm-libp2p#494)

[EvilJordan]