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 :)
IMHO you are not working on the repo (shared-folder) but on the deployed files (release folder). And there is nothing wrong in letting capistrano prepare these files through phing. Capistrano is meant for setting stuff in the deploy location (release-dir) such as these vars. I rather have these cron files prepped by capistrano in the release dir, so they are configured correctly (pure) to be potentially used by your project then copy them over to some tmp dir where all context is lost.