rename: framework huggingface-pytorch -> huggingface-pytorch-training

[dwarez]

Purpose

Rename metadata.framework from huggingface-pytorch to huggingface-pytorch-training, per review feedback on #6476. The old name is ambiguous once a huggingface-pytorch-inference family exists.

metadata.framework is a derivation key, not just a label, so four other places follow:

• test/security/data/ecr_scan_allowlist/huggingface-pytorch/ → huggingface-pytorch-training/ — ecr_scan.py resolves <dir>/<framework>/framework_allowlist.json. Without the directory rename the CVE-2026-24747 entry stops applying and the scan fails.
• huggingface-pytorch-training.pr-2.11.yml (2 lines) — path filters for that directory.
• deep_learning_container.py — --framework choices, otherwise telemetry fails in-container with invalid choice.
• docker/huggingface/pytorch/Dockerfile — ARG FRAMEWORK default, for local builds without --build-arg.

Also matches docs/src/global.yml and docs/src/data/huggingface-pytorch-training/, which already use the new name.

Second commit is not part of the rename, but clears this image's ECR scan: cryptography>=50.0.0 (CVE-2026-69247, CVE-2026-69249) and aiohttp>=3.14.3 (CVE-2026-69244), added to the existing security-floor block in docker/huggingface/pytorch/Dockerfile.

PR Checklist

• I ran pre-commit run --all-files locally before creating this PR. (Read DEVELOPMENT.md for details).