[MANOPD-88758] - add prometheus metrics for paas-geo-monitor

[Imadzuma]

Prometheus metrics support

Added prometheus metrics support for paas-geo-monitor. Added following metrics:
0. paas_geo_monitor_health as health check;

1. peer_dns_status is responsible for DNS resolution;
2. peer_svs_status is responsible for pod2service connection;
3. peer_pod_status is responsible for pod2pod connection;
   Since prometheus metrics can only take numeric values (strings are controlled by labels), used following list of possible values for each view metric:
4. 1 - successful connection/resolving;
5. 0 - connection/resolving problem;
6. -1 - can't check connection/internal error, e.g. when pod2service connection breaks, pod2pod can't be checked, because we can't take pod IP.

Status peers collects in separate threads for each peer.

New deploy parameters

Added following deploy parameters:

1. PAAS_PING_PEERS=true/false: enable/disable collecting peers statuses in background, default=true;
2. PAAS_PING_TIME=: downtime in sec between collecting statuses, default=5;
3. PAAS_DEBUG=true/false: enable/disable debug logs for troubleshooting. default=false;

Additionally:

1. Added logs support for paas-geo-monitor;
2. Fixed sm-dummy mistake;
3. Added installation parameters table for paas-geo-monitor;
4. Fixed memory leak, that happens in case of stable pinging peers:
   • Added GOMEMLIMIT env to specify soft memory limit for garbage-collector;
   • Go version was increased to 1.20 to support GOMEMLOIMIT env;
   • Keep-alive option was disabled for client connection;
   • Response body was closed after data acquisition;