chore: clear trivy and zizmor security scan findings

[mch]

Clears every finding that would fail the trivy and zizmor jobs of the security scanning gate proposed in #360. Without these changes that gate is red on arrival, and stays red on every subsequent pull request.

trivy: 83 findings -> 0

docs/sphinx/requirements.txt had drifted far behind its inputs, producing 83 vulnerabilities (47 HIGH, 2 CRITICAL), all in transitive pins: gitpython 3.1.43, tornado 6.5, pyjwt 2.8.0, urllib3 2.6.0, cryptography 42.0.7, soupsieve 2.5 and jupyter-core 5.7.2.

requirements.in only constrains rocm-docs-core, which is tracked as a git branch ref rather than a version, so the fix is a straight recompile rather than a hand-edit:

uv pip compile requirements.in --python-version 3.10 --upgrade --output-file requirements.txt

The --python-version 3.10 matches the tools.python setting in .readthedocs.yaml.

zizmor: 13 HIGH -> 0 HIGH

Three audits were failing against the two pre-existing workflows.

unpinned-uses (10 findings): every action is now pinned to the commit SHA that its current major tag resolves to, with the resolved version recorded in a trailing comment. The major versions are deliberately unchanged (actions/checkout stays on v4 rather than jumping to v7), so this is a pinning change with no behavioural difference; the upgrades are left to dependabot once the github-actions ecosystem is enabled by #360.

unpinned-images (2 findings): both container images are pinned by digest, with the floating tag retained for readability. For rocm/dev-ubuntu-22.04 the digest is also tagged 10.1.0-full, which is recorded in a comment so the ROCm version is not lost.

excessive-permissions (1 finding): id-token: write was set at workflow level in build-relocatable-packages.yml for the OIDC S3 upload, which also handed an OIDC-minting token to the release-summary job that only writes a step summary and uploads a markdown file. It now sits on the two build jobs that actually run aws-actions/configure-aws-credentials.

The 3 remaining MEDIUM artipacked findings (actions/checkout without persist-credentials: false) are left alone: they are below the gate's HIGH threshold and are a separate hardening change. The MEDIUM dependabot-cooldown finding is fixed by #360 itself.

Testing

Both scanners were run locally at the versions the security baseline pins, trivy 0.70.0 and zizmor 1.30.0, using the config files from #360.

trivy fs reports 0 vulnerabilities at every severity, down from 83, and the HIGH/CRITICAL gate exits 0.

zizmor reports 0 HIGH, down from 13.

The documentation was built twice in a Python 3.10 virtualenv, once with the old pin set and once with the new one. Both builds succeed, emit an identical set of 36 warnings, and produce the same 20 pages. The extracted article text of index.html, install/build_from_source.html and reference/presets.html is character-for-character identical between the two builds, including the 105 KB generated presets reference, despite sphinx moving from 7.3.7 to 8.1.3.

actionlint reports the same 5 pre-existing shellcheck style findings before and after the workflow changes, so no new workflow issues were introduced. All four action SHAs were confirmed against the GitHub API to be exactly the commit their version comment names, and both image digests return HTTP 200 from their registries.

[alex-breslow-amd]

LGTM