Update report to v6, bump package version to v4

What does this MR do?

• Update report from v5.1.0 to v6.0.0
• Update ruleset from v3.0.0 to v3.3.2
• Update common from v3.2.1 to v3.4.0
• Upgrade go from 1.15 to 1.22
• Update module version from v3 to v4

What are the relevant issue numbers?

Upgrade secure analyzer projects to report v6.0... (gitlab-org/gitlab#556748) • Adam Cohen

NOTE: As mentioned here, this is a breaking change, because report v6.0.0 produces reports adhering to security-report-schemas v15.2.2 which includes breaking changes. Analyzer projects upgrading to this package will need to regenerate their expectations so that the report.version field is set to 15.2.2.

Testing

Tested in Upgrade to report v6, command v4, integration-t... (kics!164 - merged) • Adam Cohen • 18.4

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 for this feature/bug
• Job definition updated, if necessary
  • Auto-DevOps template
  • Job definition example
  • CI Templates
• Conforms to the code review guidelines
• Conforms to the Go guidelines
• Security reports checked/validated by reviewer