feat(RELEASE-2035): add cpu limits to internal tasks

Set limits.cpu = requests.cpu for internal task steps to ensure
predictable resource allocation.

Changes:
- Added CPU limits to 16 internal task files
- Increased requests for high-usage steps like create-advisory,
  filter-already-released-advisory-images

Part of the same effort as managed tasks PR, split for easier
review and CI stability.

Assisted by: Cursor
Signed-off-by: Happy Bhati <hbhati@redhat.com>

Author: happybhati

tasks/internal/check-embargoed-cves-task/check-embargoed-cves-task.yaml

@@ -56,6 +56,7 @@ spec:
       computeResources:
         limits:
           memory: 32Mi
+          cpu: 20m
         requests:
           memory: 32Mi
           cpu: 20m

tasks/internal/check-fbc-opt-in/check-fbc-opt-in.yaml

@@ -77,6 +77,7 @@ spec:
       computeResources:
         limits:
           memory: 512Mi
+          cpu: 200m
         requests:
           memory: 512Mi
           cpu: 200m

tasks/internal/check-signing-certificates/check-signing-certificates.yaml

@@ -41,6 +41,7 @@ spec:
       computeResources:
         limits:
           memory: 128Mi
+          cpu: 100m
         requests:
           memory: 128Mi
           cpu: 100m

tasks/internal/collect-blob-signing-params/collect-blob-signing-params.yaml

@@ -48,6 +48,7 @@ spec:
       computeResources:
         limits:
           memory: 64Mi
+          cpu: 25m
         requests:
           memory: 64Mi
           cpu: 25m

tasks/internal/collect-simple-signing-params/collect-simple-signing-params.yaml

@@ -70,6 +70,7 @@ spec:
       computeResources:
         limits:
           memory: 64Mi
+          cpu: 25m
         requests:
           memory: 64Mi
           cpu: 25m

tasks/internal/create-advisory-oci-artifact-task/create-advisory-oci-artifact-task.yaml

@@ -66,6 +66,7 @@ spec:
       computeResources:
         limits:
           memory: 256Mi
+          cpu: 150m
         requests:
           memory: 256Mi
           cpu: 150m

tasks/internal/create-advisory-task/create-advisory-task.yaml

@@ -90,9 +90,10 @@ spec:
       computeResources:
         limits:
           memory: 256Mi
+          cpu: '1'
         requests:
           memory: 256Mi
-          cpu: '1'  # 1 is the max allowed by at least the staging cluster
+          cpu: '1'
       volumeMounts:
         - name: advisory-secret
           mountPath: /mnt/advisory_secret

tasks/internal/filter-already-released-advisory-images-task/filter-already-released-advisory-images-task.yaml

@@ -70,9 +70,10 @@ spec:
       computeResources:
         limits:
           memory: 256Mi
+          cpu: '1'
         requests:
           memory: 256Mi
-          cpu: 500m
+          cpu: '1'
       volumeMounts:
         - name: advisory-secret
           mountPath: /mnt/advisory_secret

tasks/internal/get-advisory-severity/get-advisory-severity.yaml

@@ -61,6 +61,7 @@ spec:
       computeResources:
         limits:
           memory: 128Mi
+          cpu: '1'
         requests:
           memory: 128Mi
           cpu: '1'  # 1 is the max allowed by at least the staging cluster

tasks/internal/process-file-updates-task/process-file-updates-task.yaml

@@ -84,6 +84,7 @@ spec:
       computeResources:
         limits:
           memory: 512Mi
+          cpu: 250m
         requests:
           memory: 512Mi
           cpu: 250m