Self-hosted Kura cache nodes with per-account mesh CA enrollment

Customers can now run their own Kura cache nodes in their own infrastructure, authorized by Tuist’s control plane. A new tenant-scoped credential (issued from the account’s Cache page) lets a self-hosted node introspect only its own tokens and report its own usage, and a per-account mesh CA isolates each node to its account’s mesh. Self-hosted nodes push writes into the shared managed cache through an account-level gateway and warm from the managed mesh on join, so artifacts stay consistent between the customer’s infrastructure and Tuist’s managed cache without exposing inbound connections.