Optimize cargo package step, closes #3823

Editor assessment

Using perf for a pipeline optimization — 'optimize cargo package step' — is unusual but legitimate: the type signals a performance improvement, even in CI, and the ci scope makes the context explicit. The subject is imperative, brief, and links the motivating issue via 'closes #3823'. What would elevate it is quantification: perf commits ideally state the measured gain (package step from 14 minutes to 3?), because 'optimize' is unverifiable and gives release-note readers nothing concrete. No body is present, so the technique (caching? stripping debug symbols?) must be inferred from the diff. Spec-compliant and well-scoped; just add numbers and mechanism to make the claim auditable.