docs(aibom): record the measured GKE envelope in the component values

The prior comment said neither the v1.3.0 image nor a managed control
plane had been measured against the envelope. #2310 has since measured
both: 67-69MiB at 1,001 workloads on GKE, about 45% above the Kind
figure, with steady-state CPU at 1-2m. Both stay inside the declared
requests, so the envelope holds and only the claim was stale.

Also spells out that the Kind fixtures were Deployments with replicas set
to zero, rather than the compressed 'replicas-zero workloads' phrasing,
per review feedback.

Signed-off-by: Mark Chmarny <mark@chmarny.com>

Author: mchmarny

recipes/components/k8s-aibom/values.yaml

@@ -59,10 +59,13 @@ securityContext:
   runAsUser: 65532
   allowPrivilegeEscalation: false
 
-# Measured on Kind at 0, 250, and 1,000 replicas-zero workloads. At 1,000
-# workloads, the final v1.2.0 image converged in 14s and remained below
-# 231m CPU / 49MiB. Neither the v1.3.0 image nor a managed control plane has
-# been re-measured against this envelope; that is #2310.
+# Measured on Kind at 0, 250, and 1,000 workloads, each a Deployment with
+# replicas set to zero. At 1,000 workloads the v1.2.0 image converged in 14s
+# and stayed below 231m CPU / 49MiB.
+#
+# Re-measured on GKE with the v1.3.0 image (#2310): at 1,001 workloads memory
+# reached 67-69MiB, roughly 45% above the Kind figure, while steady-state CPU
+# was 1-2m. Both stay well inside the requests below.
 resources:
   requests:
     cpu: 50m