The original dg-loader path where the JSON DGs are currently located at do not get imported into the docker image. This means that these DGs are not actually imported into the docker container.

In the Amsterdam release,  we manually placed them in the platform logic path so that they get imported in the container.

This manual approach is not sustainable and error prone, so we need to automate it such that JSON DGs are copied to deployment project and updated anytime there is a change.