fix(docker): upgrade vulnerable util-linux runtime packages

[mldangelo-oai]

Summary

• Upgrade the nine installed Debian util-linux packages affected by CVE-2026-53615 in the lightweight, full, and TensorFlow runtime images.
• Keep the existing digest-pinned Python images and targeted apt security-update strategy intact.
• Add a parameterized regression that verifies every runtime image upgrades the complete vulnerable package set.
• Document the remediation under the unreleased changelog's Security heading.

Evidence

• Docker Image CI on fix(deps): bump sqlparse from 0.5.5 to 0.6.0 #1812 failed its Trivy gate with nine HIGH findings for CVE-2026-53615: https://github.com/promptfoo/modelaudit/actions/runs/32071495279/job/95515545298
• Debian's configured trixie-security repository publishes the fixed 2.41.5-0+deb13u1 version for all nine affected packages.
• The new regression failed against all three Dockerfiles before the fix and passes for all three afterward.
• No existing open PR addresses these Debian base-image packages.

Validation

• 177 passed: Docker workflow, Docker publish, release workflow, and dependency-lock regressions.
• Repository-wide Ruff lint and formatting checks passed.
• Changelog Prettier validation and 171 post-review Docker/release tests passed.
• Changed-file mypy passed.
• Full local mypy reproduces 14 existing errors in six files unchanged from main.
• Local Docker is unavailable; the PR's Docker Image CI will build and scan all three images.
• The unrelated inherited Dependency Audit failures on current main are already addressed by fix(deps): audit all CI extras and upgrade vulnerable packages #1808.

[mldangelo-oai]

@codex review

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: 785d0339bc

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 785d0339bc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[mldangelo-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: 3e4306c597

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: 3e4306c597

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.