colony-agent internally deployed instances need a kubeconfig secret

[linear]

each of the colony-agent instances are failing to start due to a missing mgmt-kubeconfig secret in each of their respective physical clusters.

a new set of vault secrets should be set up in mgmt-24 vault to house each of the 3 kubeconfig files for the 3 workload clusters so that the agent can connect to its own workload cluster.

the goal of this issue is not necessarily to allow the agent to work in the workload cluster, though that would be a nice outcome. the goal if this is simply to allow each of the agent instances to at least to start without failing. if the apps in mgmt-24 argocd are green, this issue is complete.

[linear]

KON-30 colony-agent internally deployed instances need a kubeconfig secret