feat(CI): Build container image

[mwangggg]

related to: cryostatio/cryostat-operator#791

This CI workflow builds the agent image, then packages it in the quarkus-test sample application and pushes it to the crysotat quay repo.

example workflow in my forked -agent repo: https://github.com/mwangggg/cryostat-agent/actions/runs/8974812712

[mwangggg]

The CI successfully pushed the correct quarkus-test image into my quay repo- I tried it in cryostat3 and it works as expected.

The CI also comments the correct image in the PR

[mwangggg]

updated workflow: https://github.com/mwangggg/cryostat-agent/actions/runs/8974812712

[andrewazores]

Looking good. Could you get this to run in your fork to validate that we haven't missed anything among the recent changes? Obviously the quay.io piece won't work, unless you also set up your fork with the token secret.

[mwangggg]

I finally got a workflow that works- I completely forgot that there's no easy way to get the PR associated with a push event, so I had to remove the the safe-to-test label checking and commenting the quay image after it's been successfully pushed: https://github.com/mwangggg/cryostat-agent/actions/runs/9813147572

[andrewazores]

Ahh, yes, that makes sense. I think it's fine to just have it work on push, I don't think there will be that many PRs going on in this repo.

https://quay.io/repository/redhat-java-monitoring/quarkus-cryostat-agent?tab=tags

Workflow results look good. I think it makes sense to tag this container image with the Agent version (as your workflow did) rather than the application's own version, too.

[andrewazores]

https://github.com/cryostatio/cryostat-agent/actions/runs/9861895909/workflow