REFACTOR(resources): remove cpu limits

- to prevent throttling
Removed CPU limits from all infrastructure components while keeping
memory limits for protection:

- cnpg: removed 500m CPU limit
- external-secrets: removed 200m, 100m CPU limits (operator, webhook,
  certController)
- falco: removed 500m CPU limit (falcosidekick webui)
- vault: removed 500m CPU limit
- velero: removed 500m, 1000m CPU limits (server, node-agent)

Benefits:
- ✅ Prevents CPU throttling
- ✅ Better performance and lower latency
- ✅ More efficient resource utilization
- ✅ Simpler management (only requests to tune)

Memory limits are kept to prevent memory leaks and OOM issues.

cnpg/helm-values/cnpg.yaml

@@ -16,7 +16,7 @@ resources:
     cpu: 100m
     memory: 128Mi
   limits:
-    cpu: 500m
+    # cpu: removed to prevent throttling
     memory: 512Mi
 
 # RBAC

postgresql-dev/helm-values/postgresql-dev.yaml

@@ -26,6 +26,9 @@ resources:
   requests:
     memory: "256Mi"
     cpu: "30m"  # Reduced to 30% of original (100m -> 30m)
+  limits:
+    # cpu: removed to prevent throttling
+    memory: "1Gi"
 
 metrics:
   enabled: false

velero/helm-values/velero.yaml

@@ -13,7 +13,7 @@ resources:
     cpu: 50m
     memory: 128Mi
   limits:
-    cpu: 500m
+    # cpu: removed to prevent throttling
     memory: 512Mi
 
 # Init containers for plugins
@@ -37,7 +37,7 @@ nodeAgent:
       cpu: 30m  # Reduced to 30m to fit on mayne-worker-2 (99% CPU usage)
       memory: 256Mi
     limits:
-      cpu: 1000m
+      # cpu: removed to prevent throttling
       memory: 1Gi
 
 # Configuration for backup storage