Running run_hyperion in dev mode can break live deployment

[olliesilvester]

When playing around with Hyperion using the run_hyperion.sh script in dev mode, we managed to create log files in the Hyperion live deployment area which were owned by our own user, rather than gda2. This meant that when Hyperion was running on i03, gda2 didn't have access to write to these logs and failed.

This resulted in callbacks failing to start, so data wasn't pushed to ISPyB, and so Zocalo was never triggered. The actual error we saw in Hyperion was a timeout on waiting for Zocalo results.

We need to take a look at the run_hyperion script and decide if it's still a useful thing to have, and if so, to make sure that these logs cannot be created in the live location with the incorrect permissions

Acceptance Criteria

• run_hyperion makes it impossible to create files as a non-gda2 user in the deployment area