For OSL 1.34, we included the image-env-to-json-standalone [1] and EnvJson.schema.json [2] files as part of the kie-tools repository (packages/osl-management-console-image/).

The problem is that the image-env-to-json-standalone binary has a size of 45M and dist-git (https://pkgs.devel.redhat.com/cgit/containers/) does not allow by default to push big files like that to the repository. For OSL 1.34, productization did a workaround and was able to push the file to dist-git so the management console image was built correctly. But this requires a manual step and would be good to eliminate it.

For OSL 1.35, I think we should build those artifacts as part of maven life cycle, so they can be built on PNC like the sonataflow-management-console-webapp-image-build.zip artifact.

For the records we've tried for OSL 1.34 with PR https://github.com/kiegroup/kie-tools/pull/47 but in the end it did not work well because module `sonataflow-management-console-image`was invoking `pip3 install -r requirements.txt` which tried to install `docker` making the build to fail.

IIUC, those files like image-env-to-json-standalone are only downloaded from Node, so I believe we could have in our prod module a way just to download them and make a zip? Maybe still including in the `sonataflow-management-console-webapp-image-build.zip` but without changing the build to build `sonataflow-management-console-image` and keep building the `sonataflow-management-console-webapp` as it is now. 

[1] packages/osl-management-console-image/generated/modules/osl/management-console/added/image-env-to-json-standalone
[2] packages/osl-management-console-image/generated/modules/osl/management-console/added/EnvJson.schema.json