Petals SE Camel

When an SU has lifecycle operations happening on it, we could notify the route implementation (a Camel RouteBuilder subclass) if specific actions need to be undertaken. For example, this makes sense if a Camel route relies on some configuration file: the start action on the lifecycle could be used reload this file without the need for undeploying the whole SU. We should thus call public methods named deploy/init/start/stop/shutdown/undeploy (without any parameters) on the Camel route implementation in the corresponding lifecycle actions.