software/theia: Disable frontend forwarding from resilient clone
Until now, the resilient clone (theia1) also forwarded frontend requests from cloned embedded instances (e.g. ERP5) to the external master. This mirrored the request already sent from the main embedded instance in theia0. But since theia0 and theia1 belong to the same instance tree, from the point of view of the external master those two requests are the same.
So every time the backup instance was processed (once a day), there was a tug-of-war on this shared frontend, were theia1 would briefly overwrite its parameters to redirect to the cloned embedded instance, before thei0 would reprocess its embedded instance and tug the shared frontend back to the original embedded instance.
To fix this, frontend forwarding is now disabled for theia1. When the cloned embedded instance requests a frontend, the local proxy will now fall back to the harcoded default behavior of faking the frontend allocation by returning the original url. This allows the cloned embedded instance to instantiate normally while keeping it fully isolated.