feat: add ko test command to build with go test -c

[vincent-d]

Add a new command to build images with the output of go test -c.

It allows configuring build and LD flags in .ko.yaml with different values for build and test commands for a given importpath.

This is a new attempt at implementing #96 with a separate command.

[cpanato]

small comments for now

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

[StevenACoffman]

Oh noes! This could be helpful!

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

[clementnuss]

what is missing in this PR?

not being able to compile test binaries with ko is a blocker. hope someone finds the time to merge this 🙏🏼

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

[mkilchhofer]

@vincent-d @cpanato can we reopen this?

[mkilchhofer]

Another friendly ping @vincent-d @cpanato @imjasonh - can we reopen this?

[mkilchhofer]

@vincent-d @cpanato @imjasonh

[imjasonh]

Sorry again for the radio silence. This happens sometimes in this project due to its volunteer nature, and the relative maturity/stability of the project. I'm sorry that can also make it painful to contribute features.

If the project is moving too slow, you might consider forking to add this feature and using it "in anger" for a while, to get a feel for where there might be improvements. Since I don't anticipate using the feature myself, it's hard for me to gauge well how this should work, and how it should be implemented. I hope you understand.

If you are determined to contribute this to this project, we'll need to rebase and resolve conflicts, and I'll probably have Copilot take a first pass at a code review, if that's okay.