[M2] Resolve repository and pull Codex review follow-ups

[GaTTGeng]

Background

The M2 close audit found unresolved Codex review threads on merged repository and pull PRs. Some may already be covered by later changes, but each needs current-master verification, regression coverage where missing, a response, and thread resolution.

Review threads

• PR feat(repo): align repository configuration cache #167: normalize configured URLs before cache-name lookup
• PR feat(repo): align repository configuration cache #167: preserve server-provided intermediates during custom-CA validation
• PR feat(action): add M2 operation request objects #173: keep credentials scoped for direct archive URLs
• PR feat(action): add M2 operation request objects #173: verify requested chart digests before extraction
• PR feat(action): add M2 operation request objects #173: honor destination/untar options
• PR feat(repo): align traditional chart pull behavior #175: use request credentials when fetching configured repository indexes
• Re-review the combined fix(action): normalize packaged chart metadata #182/fix(repo): harden repository state persistence #183 result because those PRs were merged before Codex completed review

Acceptance

• Verify every item against current master; do not duplicate already-integrated fixes.
• Add regression tests for every behavior that still lacks coverage.
• Reply to and resolve all associated review threads.
• Full Release suite and packaging pass.
• A follow-up PR receives final Codex review; 👀 is pending, 👍 is complete.