Revert "drop -m flag" to fix empty SBOM generation in v0.18.0

[0xiso]

This reverts commit 3f2f5a5.

Since ko v0.18.0, mostly empty SBOMs have been generated. While investigating the cause of this, I noticed that the -m flag was removed from go version -m by commit 3f2f5a5. If the -m flag is not specified, module versions are not outputted, resulting in the generation of SBOMs that do not include module information.

$ go help version
usage: go version [-m] [-v] [file ...]
[...]
The -m flag causes go version to print each file's embedded
module version information, when available. In the output, the module
information consists of multiple lines following the version line, each
indented by a leading tab character.

This PR resolves this issue by reverting the commit that removed the -m flag. As far as I tested, the output of go version -m did not differ between Go 1.23 and Go 1.24.0.

[imjasonh]

Thank you!

[0xiso]

Oh, when an invalid non-Go binary file is passed to go version -m, Go 1.23 returns a 0 exit code, but Go 1.24 returns 1, which is causing tests to fail. This seems to be an issue with the tests themselves, so the test code will likely need to be fixed.