feat(preset): add protectProc preset

[rksharma95]

adds a preset protectProc that can enforce (audit or block) policy on /proc directory access by non-owner process.

example ksp policy:

apiVersion: security.kubearmor.com/v1
kind: KubeArmorPolicy
metadata:
  name: ksp-nginx-presets
spec:
  presets:
  - action: Block
    name: protectProc
  selector:
    matchLabels:
      app: nginx
  severity: 3

simulating policy violation:

kubectl exec -it nginx-5678bf4f67-l4hcg -- bash
root@nginx-5678bf4f67-l4hcg:/# sleep 1000&
[1] 263
root@nginx-5678bf4f67-l4hcg:/# ls /proc/263
ls: cannot open directory '/proc/263': Permission denied

alert generated for policy violation

== Alert / 2025-03-26 12:45:58.285429 ==
ClusterName: default
HostName: archlinux
NamespaceName: default
PodName: nginx-5678bf4f67-l4hcg
Labels: app=nginx
ContainerName: nginx
ContainerID: 70aca5b90adececbe559ec9981fa2920c063319e9133d1c12e067b62b42b1080
ContainerImage: docker.io/library/nginx:latest@sha256:124b44bfc9ccd1f3cedf4b592d4d1e8bddb78b51ec2ed5056c52d3692baebc19
Type: MatchedPolicy
PolicyName: ksp-nginx-presets
Source: /usr/bin/ls
Resource: /proc/263
Operation: File
Enforcer: PRESET-ProtectProcPreset
Result: Passed
Cwd: /
HostPID: 152784
HostPPID: 152681
Owner: map[Name:nginx Namespace:default Ref:Deployment]
PID: 275
PPID: 152681
UID: 0

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[rksharma95]

denying symlink /proc/* access

root@nginx-676b6c5bbc-frx9l:/tmp# ls -l /proc/41/fd/0
lrwx------ 1 root root 64 Apr  2 08:14 /proc/41/fd/0 -> /dev/pts/0
root@nginx-676b6c5bbc-frx9l:/tmp# cat /proc/41/fd/0
cat: /proc/41/fd/0: Permission denied
root@nginx-676b6c5bbc-frx9l:/tmp# cat /proc/self/fd/0
hello
hello
^C

alert

== Alert / 2025-04-02 08:31:10.185986 ==
ClusterName: default
HostName: archlinux
NamespaceName: default
PodName: nginx-676b6c5bbc-frx9l
Labels: app=nginx
ContainerName: nginx
ContainerID: 05eb0693b5363458e09f5c1b9644a9eea9ae61377751776fb8d55bbc8d0bc2eb
ContainerImage: docker.io/library/nginx:latest@sha256:124b44bfc9ccd1f3cedf4b592d4d1e8bddb78b51ec2ed5056c52d3692baebc19
Type: MatchedPolicy
PolicyName: ksp-nginx-protect-proc-preset
Source: /usr/bin/cat /proc/41/fd/0
Resource: /proc/41/fd/0
Operation: File
Enforcer: PRESET-ProtectProcPreset
Result: Permission denied
Cwd: /
HostPID: 145285
HostPPID: 140744
Owner: map[Name:nginx Namespace:default Ref:Deployment]
PID: 964
PPID: 140744
ParentProcessName: /usr/bin/bash
ProcessName: /usr/bin/cat
UID: 0

[Aryan-sharma11]

Looks good, minor nits to address