fix(server): use pod-name:pod-ip as node identity for kubearmor daemon

[rksharma95]

to avoid the case, if kubearmor pod recreated for any reason and pod deletion event received after pod added event then node will be removed from current list of nodes/kubearmor-pods if node id is created using node-ip only.

{"level":"warn","ts":"2024-11-21 13:42:55.674541","caller":"log/logger.go:79","msg":"failed to receive an alert (192.168.29.159:32767) rpc error: code = Unavailable desc = error reading from server: EOF"}
{"level":"info","ts":"2024-11-21 13:42:55.674623","caller":"log/logger.go:54","msg":"Destroyed the client (192.168.29.159:32767)"}
{"level":"warn","ts":"2024-11-21 13:42:55.674978","caller":"log/logger.go:84","msg":"Failed to call WatchMessages (192.168.29.159:32767) err=rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 192.168.29.159:32767: connect: connection refused\"\n"}
{"level":"info","ts":"2024-11-21 13:42:55.874444","caller":"log/logger.go:54","msg":"[addevent] pod kubearmor-bpf-containerd-98c2c-4krn9 has been added"}
{"level":"info","ts":"2024-11-21 13:42:56.273261","caller":"log/logger.go:54","msg":"[deleteEvent] pod kubearmor-bpf-containerd-98c2c-s9bnk has been deleted"}
{"level":"info","ts":"2024-11-21 13:42:56.273329","caller":"log/logger.go:54","msg":"pod with nodeip 192.168.29.159 deleted"}

[rksharma95]

/review @anurag-rajawat

[rootxrishabh]

The fix looks good. Nice work 👍

[DelusionalOptimist]

LGTM.