feat(libp2p): validate config options at startup

[sharmis-tp]

Description

Related #1573

Adds config validation to the libp2p package only, as suggested on the issue; other modules can follow. validateConfig() now checks the options this package consumes directly with a valibot schema and fails fast with an InvalidParametersError that names the field, e.g. "Invalid libp2p config: addresses.listen.1 is not a valid multiaddr: foo".

Validated: address lists (listen, announce, noAnnounce, appendAnnounce, connectionManager.allow/deny) must parse as multiaddrs; connection manager limits and timeouts must be non-negative numbers (Infinity allowed); maxConnections must be > 0; connectionMonitor flags must be booleans; transportManager.faultTolerance must be a FaultTolerance value. Unknown keys are allowed so services keep their own options.

Notes & open questions

• Library choice and bundle sizes are in the issue comment: valibot adds about 1.5 KB gzip to the browser bundle.
• Multiaddr instances are accepted in address lists because the address manager already calls toString() on them.
• The existing "maxConnections must be greater than 0" wording is kept, so the connection manager test still passes.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works