Fail if Swarm.ConnMgr.HighWater is above Swarm.ResourceMgr hard limits

[BigLep]

Done Criteria

User get a clear message to the console and a terminated process if their Swarm.ConnMgr config has know issues. Specifically:
if the resource manager is enabled,Swarm.ConnMgr.HighWater must be below Swarm.ResourceMgr.System.Conns and (Swarm.ResourceMgr.System.ConnsInbound + Swarm.ResourceMgr.System,ConnsOutbound).

• Code change (above) fix: refuse to start if soft ConnMgr limits are bigger than hard ResourceMgr limits #9560
• Docs update: https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmconnmgr

Why Important

If the soft connection manager limits are above the hard resource manager limits, then the soft connection manager will never kick in and there will be a confusing user experience.

This is a footgun that Kubo maintainers have observed during the 0.18RC phase.

Similar to #9546, Swarm.ConnMgr has been present in Kubo for years and users have adjusted this value for their usecses. While #9546 should help, it's still possible that a user's ConnMgr and ResourceMrg limits aren't configured appropriately relative to each other. This acts as a backstop to catch this case.

Notes

• There is a backlog item in go-libp2p to better connect the connection manager and resource manager: Reconcile Conn manager's hi/lo watermarks and the resource manager's limits libp2p/go-libp2p#1640 . To control the experience, we're solving this at the Kubo level with this issue.

[ajnavarro]

@Jorropo I assigned it to you because you moved it from TODO to In Progress, to avoid confusion.

[BigLep]

@Jorropo @lidel : I saw we have the code change in #9560 . What about the docs change for https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmconnmgr ?