chore(ci): build images with dockerfile instead of ko

[mikhailswift]

Our Dockerfile includes our migrations and Atlas to execute those migrations. However, the public image we are pushing is built with Ko and excludes these files/tools. This commit switches gorelease to build the image with the included Dockerfile.

What this PR does / why we need it

Description

Which issue(s) this PR fixes (optional)

(optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged)*

Fixes #

Acceptance Criteria Met

• Docs changes if needed
• Testing changes if needed
• All workflow checks passing (automatically enforced)
• All review conversations resolved (automatically enforced)
• DCO Sign-off

Special notes for your reviewer:

[kairoaraujo]

@mikhailswift
I'm trying to understand this error here https://github.com/in-toto/archivista/actions/runs/10045026639/job/27762025317?pr=332
I think is because the previous error (I retriggered)

[colek42]

We can use this feature with KO. https://github.com/ko-build/ko/blob/main/docs/features/static-assets.md

Since we are using KO for dev previews in JUDGE, and KO does not require Docker I think we should try this.

[mikhailswift]

@mikhailswift I'm trying to understand this error here https://github.com/in-toto/archivista/actions/runs/10045026639/job/27762025317?pr=332 I think is because the previous error (I retriggered)

This error is happening because the witness-run-action installs witness to the current working directory, which overwrites archivista's README.md and LICENSE file with the one packaged in witness.tar.gz, causing a dirty git tree. I have a PR out for the witness-run-action to add an option to install witness to a user defined directory.

testifysec/witness-run-action#13