Fix application profile and NN patching

[amirmalka]

Overview

Bug fix:

• Application profiles and network neighborhoods were not marked as too big when passing the resource size threshold, due to a bug in the logic. The existing patch logic would exit from the function whenever the status annotation exists (regardless of its value).
• monitorContainer function now returns the error - so that a log message with the reason will be printed to the log.

Logs after the fix:

{"level":"debug","ts":"2024-08-06T12:21:03Z","msg":"ApplicationProfileManager - saved application profile","capabilities":3,"execs":10,"opens":138,"slug":"pod-ping-app","container index":0,"container ID":"ee8d0d98e0700c349ab01565bcb2fff3ddca66bb3a8eb0aa7d6c240c33cebf00","k8s workload":"default/ping-app/ping-app"}
{"level":"debug","ts":"2024-08-06T12:21:03Z","msg":"ApplicationProfileManager - object is too large"}
{"level":"info","ts":"2024-08-06T12:21:03Z","msg":"ApplicationProfileManager - stop monitor on container","reason":"object is too large","container index":0,"container ID":"ee8d0d98e0700c349ab01565bcb2fff3ddca66bb3a8eb0aa7d6c240c33cebf00","k8s workload":"default/ping-app/ping-app"}

Application profile (setting the max size to 12):

kubectl get applicationprofiles pod-ping-app -oyaml
apiVersion: spdx.softwarecomposition.kubescape.io/v1beta1
kind: ApplicationProfile
metadata:
  annotations:
    kubescape.io/completion: complete
    kubescape.io/resource-size: "148"
    kubescape.io/status: too-large
    kubescape.io/wlid: wlid://cluster-xxxx/namespace-default/pod-ping-app
  creationTimestamp: "2024-08-06T12:18:55Z"
....

[github-actions]

Summary:

• License scan: success
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success