Xcode cache daemon inherits cache endpoint and feature flags from the parent

The Xcode cache daemon now sees the same TUIST_CACHE_ENDPOINT and TUIST_FEATURE_FLAG_* values that the parent process sets. Previously the launchd-managed daemon did not inherit them and resolved the public endpoint via getCacheEndpoints, so on hosts with a private-network xcode-cache node, the module cache used the private node while the CAS round-tripped every compilation unit to the public endpoint over the WAN, leaving the Xcode cache net-negative on a full compile. Forwarding the override and feature flags lets the daemon resolve the same private cache the rest of the CLI uses.