Processor deployments no longer crashloop on a missing license key

In managed Tuist deployments, the build and xcresult processor pods no longer crashloop on startup with a missing license key. The Helm chart now includes the tuist.licenseEnv template in both processor deployments, so they receive TUIST_LICENSE_KEY from the same External Secrets Operator secret the server Deployment and migrate Job already use. Self-hosted installs that don’t configure a license source are unaffected, because tuist.licenseEnv only emits the variable when a license is configured.