Processor deployments now receive the Tuist license key in Helm 0.12.2

The Helm chart now passes the TUIST_LICENSE_KEY environment variable to the build and xcresult processor deployments by including the shared tuist.licenseEnv template in both processor-deployment.yaml and xcresult-processor-deployment.yaml. Previously these pods relied on an encrypted blob for the license key, which has since been removed, causing the processors to crash on boot with a missing license error. With this fix, managed Tuist deployments boot the build and xcresult processors successfully, and self-hosted installs with a configured license source now supply the key to the processors as well.