ops,ci: docker buildx bake, fix publish/release flows

[protolambda]

Description

In #7715 we changed the docker build system to build the following modules with a shared docker image, to reduce CI work and improve cache usage:

• op-heartbeat
• op-challenger
• op-node
• op-batcher
• op-proposer
• op-program
• op-wheel

Most of these we also publish (everything except op-wheel), and release (everything except op-program and op-wheel).

However, we were building the same docker images with 3 different job definitions that then had to correctly invoke the docker build.

To try and fix that, I unified the docker_build / docker_publish / docker_release jobs, since most of the parameters and work overlaps.

With new publish and release job parameters (boolean flags) the job can do the steps for publishing/releasing conditionally.

And to reduce the CI configuration more, I moved the docker configuration of all the targets into a docker-bake setup (see docker-bake.hcl): see make golang-docker for an example that builds the common op-node op-batcher op-proposer op-challenger targets.

[mslipper]

LGTM

[trianglesphere]

The CI workflow is now failing. I'm not sure why, but it's in the op-stack-go-docker-build-1 step and looks like it's caused by these changes.

[tynes]

As long as we are ok with depending on an experimental feature, i am cool with this
https://docs.docker.com/build/bake/

approved in slack