chore(deps): bump golang.org/x/vuln from 1.0.4 to 1.1.2 (backport #558)

[mergify]

Bumps golang.org/x/vuln from 1.0.4 to 1.1.2.

Release notes

Sourced from golang.org/x/vuln's releases.

v1.1.2

This release brings the support for the VEX output format.

Integration

Govulncheck now supports OpenVex output format via -format openvex flag option. Please see here for more details on the actual encoding.

v1.1.1

This release brings some minor improvements to govulncheck textual output and performance optimizations for package and module scan modes.

The major change brought by this release is the support for SARIF output format.

Integration

Govulncheck now supports Static Analysis Results Interchange Format (SARIF) output format via -format sarif flag option. Please see here for more details on the actual encoding.

v1.1.0

This release brings minor improvements to govulncheck inner workings and a few bug fixes (#66139, #65590).

Integration

Govulncheck JSON now also contains scan mode as part of the Config message.

Further, the Position in trace frames now contains only paths relative to their enclosing module. This could potentially break some existing clients, hence the bump of the minor version.

Note that this change is made to allow for easier preservation of privacy by the clients as now the file positions do not contain information about the local machine. This is also a portable solution. Clients can reconstruct full paths for their local machine by joining the Position relative paths with paths of the enclosing modules on the local machine.

Commits

• 3740f5c internal/osv: add review status
• 29462d7 vulncheck: update documentation for vex
• 2736e1d cmd/govulncheck/integration/stackrox-scanner: update expectations
• 65c6e2b cmd/govulncheck/integration/k8s: update expectations
• 03e66a6 internal/govulncheck: add more comments for emitted OSVs
• f30059c go.mod: update golang.org/x dependencies
• 84735a3 internal/scan: increase telemetry counter for show flag
• fb2a687 internal/scan: add format and scan level telemetry
• f5e77b8 internal/cmd/govulncheck: remove unnecessary binary dependency
• 1201340 cmd/govulncheck/integration: update go in integration tests
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

This is an automatic backport of pull request #558 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 242fdf2 has failed:

On branch mergify/bp/release/v1.x.x/pr-558
Your branch is up to date with 'origin/release/v1.x.x'.

You are currently cherry-picking commit 242fdf2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally