feat(manager): don't fetch peers from network-contact file

[RolandSherwin]

• Currently, the launchpad uses PeersArgs to optionally accept --peers or SAFE_PEERS env variable, but it had the network-contacts feature turned on for sn_peers_acquistion. This means that when you launch the TUI normally, the bootstrap peers were obtained from the contacts file and were being hard-coded inside the service definition file.
• This is bad because, if there is a change in the network-contacts file (say our original bootstrap peers crashed), then the services started with the hardcoded values will have no way to contact the updated boostrap peers.
  • They'd fail to connect
• Also, it is bad because service definition file might not sometimes support a large list of values. This might have been a reason for some nodes not being started.

Changes:

• Modified the manager to not get the network-contact peers

For future PR:

• remove the network-contacts feature from node-launchpad. This would require making some tweaks to sn_peers_acquistion to expose a function there. This Allow safenode-manager's nat detection command to use the default server list URL #1800 is related.