Fixes issues caused by recent refactorings from v1.3.3

Merge branch 'release/v1.3.4' into develop
only change permissions if the path exists
Don't copy over config files that already exist
Dumps the database to the tmp backup directory

No more mess in the current_release directory. Especially if the directory
isn't owned by the ssh user for some odd reason (like if you're hosting with
Blackmesh).
fix documentation error in array syntax
Adds dependency check for rsync on remote hosts
more flexibility in creating config files for all necessary environments
aint nobody got time for spelling bees
Dump the database to the tmp backups directory

Instead of dumping the database to the current release directory
we'll dump it to :deploy_to/backups/tmp/:release_name/ directory
which should be then zipped up in the backup:web task
Closes #47

Rescue from exceptions, log them and keep the process going rather than
being a jerk and blocking a deploy for something as simple as backing up
code.
Again, should only be ran if the directory exists
Adds ability to enable/disable modules on deploys

Adds variables (:enable_modules, :disable_modules) with a default Ash_Bar
module (that we use internally at this time) that shouldn't be run in
staging or production environments.
Version bump to 1.3.5
Refactor use of try_sudo in favor of sudo

Looks like the issue of try_sudo not prompting or not allowing
interactive input is caused by the `ssh_options[:pty]`

https://github.com/capistrano/capistrano/issues/474#issuecomment-22615962
Closes #48

Refactored use of try_sudo to go back to previous working code that
was using `run "#{sudo} ..."`

This rollback will stay like this until we refactor the capistrano-ash gem
with better testing (and upgrades to capistrano 3.x) or someone truly has
a way for try_sudo to consistently work with either prompting for a password
or some other work around.
oops...missed a try_sudo
Make sure ssh user owns the var folder
Create throw away git repo after deploy for paranoid developers who need to track file-level changes
add triggers and stored procedures to be dumped
Create robots.txt file for SEO per environment