Added "No-Op" deploy strategy

Development using Vagrant VMs is quite common so far. Still, some tasks should be executed automatically both on dev and test/prod environments, so it makes sense to write Capistrano tasks for them. This deploy strategy allows to have a network mount (NFS, Virtualbox shared folders or anything else) to share the source code with the VM, and allows developers to write/work with capistrano tasks and test them locally before using them to production, retaining the ability to change code on-the-fly and see the effects immediately on the VM.
By default, it uses the "repo" folder, as used by the other SCM classes.
Basically, this strategy does nothing except for creating a symlink to the "repo" folder every time the deploy is executed, then the "current" symlink can be created. Yeah, a symlink pointing to a symlink is not the best, but...better ideas?