Make sure that cronfiles are also filtered with expandproperties if run under sudo

We noticed that cronfiles copied using the sudo method were not replace (which is rather logical).

This way they are first copied to a temporary directory in order to replace the variables in the files, then copied from there to the cron directory under sudo user.

@ngroot :)
With the word "repo" i meant the deployed version. We're editing data there. If you'd need the pure cron file within your project, you would open up ``${cron.files}``. If you want the replaced / filled cron files, you'd have to parse them yourself or open up ``${cron.location}``. I'm just not a big fan of editing those files inside the deployed version. I wonder what your opinion on this is, @ngroot :)