We cannot feasibly shadow every Env var that a user may wish to set for the template. E.g., what if they need to specify QUARKUS_PACKAGE_TYPE, do we hard-code that as a template parameter? Or every Env var that is used to configure the run script?

Investigate how we can permit arbitrary env vars to be incorporated into the template and passed through to the relevant stages.