Keeping container-builder and kogito-serverless-operator in different repositories has been proven counter-productive (one has to open two PRs to implement a feature). We should archive container-builder and add it to the kogito-serverless-operator repository in a different go module.

Others can still import it since it's a different go module.

In the future, if the container-builder takes flight alone, we can consider splitting it again.