Prevent k8s Hyperion from executing at the same time as non-k8s

When Hyperion is running in UDC mode, it is possible that if both a standard server-installed instance of Hyperion and a kubernetes instance are running, that they could both attempt to run jobs from Agamemnon simultaneously.

Probably the best way of preventing this is for k8s and non-k8s Hyperion instances to use different baton user names, and for GDA to grant access to the correct instance according to some property.

## Acceptance Criteria
- K8s and non k8s Hyperion instances can't both process agamemnon instructions at the same time.
- `hyperion_restart()` invocations are transparently sent to the correct hyperion instance via configuration