Go images are defined in 2 places. It prevents an esay Golang version upgrade

In https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-templates/-/blob/main/templates/operator-template.yml?ref_type=heads, there 2 go images:

• One to build the operator, relying on ToBeContinuous and explicitely refering to the Golang version
• One to deploy the operator. This image is build in https://gitlab.com/sylva-projects/sylva-elements/container-images/ci-image/-/blob/main/ci-operator-image/Dockerfile?ref_type=heads

It creates the following issues:

• In a repo building an operator (today, there 3 such repos), one can not simply refer to a new GO_IMAGE verion to build and deploy
• The 2nd image tag does no refer directly to Golang version. Upgrading it only (and equaling GO_IMAGE to it) would not trigger go.mod upgrade automatically

Solutions may be

• Deploy without go (pure kubectl apply) ?
• ?