Require updated ACL and attr packages in the BCI runtime

[ai-collaboration-app]

Require libacl1 >= 2.4.0-150000.4.6.1 and libattr1 >= 2.6.0-150000.4.3.1 when assembling the BCI runtime, and align the package-install stage with the runtime's SLES 15.7 release. An unavailable minimum now fails the build instead of silently retaining an old package; newer SUSE updates remain allowed. A current rebuild already obtains these versions, and the explicit requirements prevent regression to the shipped versions.

Tracking: https://github.com/StackVista/cve-reporter/issues/69. Mission-control scripts/cve_scan_findings.rb verified run 35083378323, attempt 1, aggregate sha256:442de95bc14003d309ac7ada8121d91efe902c8d46ce8dcf38c4c0c08381aa93. This change addresses its six libacl1/libattr1 rows for CVE-2026-54369, CVE-2026-54370 and CVE-2026-54371.

Validation on signed head 3caadff, based directly on master c028f24:

• CI 35085371983: amd64 and arm64 generated-code/module verification, lint/vet, unit tests, build, and OpenPGP absence checks passed. Both BCI image builds and binary-version/healthcheck smoke tests passed. All eight required jobs passed, including signed architecture and multi-architecture publication.
• amd64 image evidence and arm64 image evidence: both install libacl1 2.4.0-150000.4.6.1 and libattr1 2.6.0-150000.4.3.1; all six target findings absent from Trivy/Grype, and separate Trivy secrets scans report none.
• A fresh local Grype 0.117.0 scan reproduces all six target rows in the shipped c028f242 image. An impossible version constraint (libacl1>=999.0) returns nonzero, confirming the package minimum fails closed.
• Local Docker assembly succeeded but image export twice failed on a containerd writer lock; an alternate filesystem export stalled and was stopped. No local candidate scan or smoke success is claimed; complete CI images provide those checks.

Published candidate: quay.io/stackstate/stackstate-k8s-process-agent:3caadff5, OCI index sha256:94c81a3c1faa1fe09d23a3f4d6f0c530476e953570c4eb3f1eb0a7421fbd1aac. Both platform manifests carry revision 3caadff580c0192c40a09d4a96460a0815901381:

Platform	Immutable manifest	Target findings in fresh Grype 0.117.0
amd64	sha256:57e75f0abb352e550e375516bef8a8fad22030c6a995f678bd87264f2c0bf8b0	0
arm64	sha256:764b7d4ce5bc56621e15bae48ac75241ff1ebe398b73481c8761f370d1237438	0

The amd64 publication log and arm64 publication log independently confirm the fixed package versions during the publication rebuild. The direct registry scans used Grype DB built 2026-09-16T06:30:57Z, without VEX, via grype registry:quay.io/stackstate/stackstate-k8s-process-agent@<manifest> --platform linux/<arch> -o json. Both retain exactly five Go findings: GHSA-2v4p-qf9q-27wj (HIGH), GO-2026-5064 and GO-2026-5338 (CRITICAL), GHSA-7jxh-36q5-gcqv and GO-2026-5622 (MEDIUM). This does not approve their applicability or suppression.

Residuals: both CI evaluators report 3 in-scope, 2 unmanaged, 1 expired: CVE-2026-84445 (gRPC), CVE-2026-53495 (containerd), and GO-2026-5932 (expired 2026-09-10). Inform-mode CVE policy and blocking secrets checks are unchanged. SUSE preserves legacy pathname APIs and adds safer APIs, so this is a package update, not an assertion that every possible downstream caller is race-free.

PR #278 remains at c484046 with its existing green CI 34503849617; PR #287 is untouched. No Go module, VEX or exception changes. Containerd Critical applicability and GO-2026-5932 remain human decisions under #27. Independent review, human merge, and a later delivery scan remain outstanding; this candidate is not closure evidence.