fix(trivy): use the RPM report templates at their default paths
Change and owner scope
Closes #504 (closed).
- Use the signature-verified Trivy RPM's static
/usr/local/share/trivy/templates/gitlab.tplandhtml.tplpaths directly; remove copied templates and keep only the guarded in-place JSON URL-encoding correction. - Preserve vulnerability findings, filtering and scan policy. Retain the existing native reference/encoding regression suite.
- Qualify complete current-source CI, connected workflows and every owned teardown before guarded owner review.
Qualified but unmerged prerequisites !694 (closed) and !695 (merged) are included explicitly. Delivered main supplies its exact-tree lint correction.
Acceptance evidence
Complete source CI and all 64 component children succeed. The executed merge tree exactly matches the current source and includes fresh main. The actual rebuilt-image report suite passes all nine retained cases, including rejected leading/interior/trailing references and JSON encoding; housekeeping passes 32 cases and shell regressions pass 94. Required image builds/scans, both actual connected workflow lifecycles, documentation build/lint and pipeline support checks pass.
All six applicable cleanup traces are checked: exact Helm/ZAP namespace deletion, both ArgoCD application/configmap cleanups, native Molecule destruction, and the existing ephemeral Gruyere no-resource teardown. Intentionally failing legacy/SonarQube test fixtures retain their existing documented policy; no required check is bypassed or made optional.
The final 14-file task/prerequisite diff and rendered Trivy guide are reviewed. Every discussion page and recent top-level note is checked; the latest owner request for static RPM paths is implemented with no unresolved feedback.
Definition of Done
- Nothing remains within the requested implementation and acceptance scope.
- Acceptance criteria and latest owner instructions are met.
- Changes are limited to the task and explicit qualified prerequisites.
- Required code, configuration, builds, scans and complete pipeline pass.
- Existing meaningful native report and negative-path tests execute successfully in CI.
- Final diff, fresh target and all feedback are reviewed; no rebase is needed.
- Last source pipeline succeeds and all owned cleanup is verified.
- Documentation is updated and its rendered page is checked.