Sniffer unable to start if health port already in use

[majikman111]

In our cluster, we have a variety of nodes without various services attached and occasionally port 9090 is already in use, which causes the sniffer to terminate with the following error

{"level":"info","msg":"starting error telemetry for component 'NETWORK_MAPPER' with version 'v2.0.15'","time":"2024-12-12T16:19:53Z"}
{"level":"info","msg":"error reporting disabled","time":"2024-12-12T16:19:53Z"}
http server started on [::]:2112
{"error":"http: Server closed","level": "error","msg":"Error when starting metrics server, however not returning an error as this may be due to the same port being used on the host node, and the sniffer runs in hostNetwork mode.","time":"2024-12-12T16:19:53Z"}
{"error":"listen tcp :9090: bind: address already in use","level": "panic","msg":"Error when running server or HTTP server.","time":"2024-12-12T16:19:58Z"}

Error source:
https://github.com/otterize/network-mapper/blob/main/src/sniffer/cmd/main.go#L106

As it is not required for the sniffer, the health server port should either be configurable per deployment or allowed to fail like the metrics server without crashing the sniffer (possibly as a configurable opt-in setting)