Increase target peers to 100, max peers to 110

[twoeths]

Problem description

Gradually all nodes will subscribe to exactly 2 subnets per node due to ethereum/consensus-specs#3312 so it'll not easy to find enough subnet peers

Solution description

We should track different things:

• Is it over 110 peers at some time, what's the consequence of that Lodestar has more than 55 peers #5732
• Network volume, especially when we join a sync committee, only do it once we resolve I/O performance issue when subscribing to sync committee #5741 ?
• Track time to publish a message, especially messages on core topics. See feat: track time to publish a message js-libp2p-gossipsub#451

Additional context

Also other clients already increased to 100 peers (lighthouse, nimbus), lodestar should do the same

[dapplion]

@tuyennhv we should review the flood publish strategy into publishing to only a subset of subscribed peers. Can you review other clients strategies? Nimbus runs nodes with 2500 peers and has very reasonable outbound bandwidth

[philknows]

• blocked on Lodestar has more than 55 peers #5732

[twoeths]

need to figure out if it causes more delay when publishing block or not when increasing to 100 peers because we send published messages to all peers, see #6596

[twoeths]

need to also take heap snapshot of network thread (when it's >= 2GB) + main thread (after increase target peers to 100). See #6556 (comment)