Add Go stdlib remediation guidance for CS in Trivy template
What does this MR do?
Adds proper remediation guidance for Go stdlib vulnerabilities in container scanning reports.The guidance is now visible in the UI, so users can see actionable instructions directly when reviewing vulnerabilities.
Why is this needed?
Previously, users were shown messages suggesting they update stdlib directly, which is technically incorrect because the stdlib is bundled with the Go compiler. Users must instead upgrade the Go base image and rebuild their binaries. This MR ensures the remediation guidance in the UI is more accurate and actionable.
What are the relevant issue numbers / merge requests ?
Screenshots
| Before | After |
|---|---|
 |
 |
- You can see the updated solution text in this security pipeline: https://gitlab.com/gitlab-org/secure/tests/albi.yusupova/test-541028/-/pipelines/2034944214/security.
- And the current one in here: https://gitlab.com/gitlab-org/secure/tests/albi.yusupova/test-541028/-/pipelines/2017363841/security
Does this MR meet the acceptance criteria?
- Changelog entry added
- Documentation created/updated for GitLab EE, if necessary
- Documentation created/updated for this project, if necessary
- Documentation reviewed by technical writer or follow-up review issue created
- Tests added
- Job definition updated, if necessary
- Conforms to the code review guidelines
- Conforms to the Go guidelines
- Conforms to the Ruby guidelines
- Security reports checked/validated by reviewer
Closes #541028